Skip to content

Commit

Permalink
Add note about limitations of macOS export from Windows.
Browse files Browse the repository at this point in the history
  • Loading branch information
bruvzg committed Sep 8, 2024
1 parent bf4c8bd commit 13f05b1
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions tutorials/export/exporting_for_macos.rst
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ macOS apps exported with the official export templates are exported as a single
This bundle can be exported as is, packed in a ZIP archive or DMG disk image (only supported when exporting from a computer running macOS).
`Universal binaries for macOS support both Intel x86_64 and ARM64 (Apple silicon, i.e. M1) architectures <https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary>`__.

.. warning::
Due to file system limitations, raw ``.app`` bundles exported from Windows lack ``executable`` flag and won't run on macOS.
To fix it, use the ``chmod +x {executable_name}`` command after transferring the exported ``.app`` to macOS or Linux. Projects exported as ``.zip`` aren't affected by this issue.
The main executable located in the ``Contents/MacOS/`` subfolder, as well as optional helper executables in the ``Contents/Helpers/`` subfolder, should have ``executable`` permission for the ``.app`` bundle to be valid.

Requirements
------------

Expand Down

0 comments on commit 13f05b1

Please sign in to comment.