You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorials/export/exporting_for_macos.rst
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,18 @@ Exporting for macOS
10
10
read :ref:`doc_compiling_for_macos`.
11
11
12
12
macOS apps exported with the official export templates are exported as a single "Universal 2" binary ``.app`` bundle, a folder with a specific structure which stores the executable, libraries and all the project files.
13
-
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).
13
+
This bundle can be exported as is, packed in a ZIP archive, or packed in a DMG disk image (only supported when exporting from macOS).
14
14
`Universal binaries for macOS support both Intel x86_64 and ARM64 (Apple Silicon) architectures <https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary>`__.
15
15
16
16
.. warning::
17
-
Due to file system limitations, raw ``.app`` bundles exported from Windows lack ``executable`` flag and won't run on macOS.
18
-
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.
19
-
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.
17
+
Due to file system limitations, ``.app`` bundles exported from Windows lack the
18
+
``executable`` flag and won't run on macOS. Projects exported as ``.zip`` are not
19
+
affected by this issue. To run ``.app`` bundles exported from Windows on macOS,
20
+
transfer the ``.app`` to a device running macOS or Linux and use the
21
+
``chmod +x {executable_name}`` terminal command to add the ``executable`` permission.
22
+
The main executable located in the ``Contents/MacOS/`` subfolder, as well
23
+
as optional helper executables in the ``Contents/Helpers/`` subfolder, should have
24
+
the ``executable`` permission for the ``.app`` bundle to be valid.
0 commit comments