From 2a1cf124503b9aae6ceb77226d8e03f48cde6313 Mon Sep 17 00:00:00 2001 From: bruvzg <7645683+bruvzg@users.noreply.github.com> Date: Sat, 7 Sep 2024 20:11:22 +0300 Subject: [PATCH] Add note about limitations of macOS export from Windows. --- tutorials/export/exporting_for_macos.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tutorials/export/exporting_for_macos.rst b/tutorials/export/exporting_for_macos.rst index ddc3c60a4e7e..aa6d1ec04992 100644 --- a/tutorials/export/exporting_for_macos.rst +++ b/tutorials/export/exporting_for_macos.rst @@ -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 `__. +.. 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 ``chmod +x {executable_name}`` command after transferring the exported ``.app`` + to macOS or Linux. Projects exported as ``.zip`` aren't affected by this issue. + Main executable located in the ``Contents/MacOS/`` subfolder, optional helper executables in the ``Contents/Helpers/`` subfolder. + Requirements ------------