From 158764866e06762759d546ba6721348710a3f8f1 Mon Sep 17 00:00:00 2001 From: tom <98792+pandrr@users.noreply.github.com> Date: Mon, 15 Apr 2024 14:28:49 +0200 Subject: [PATCH] Update export_exe.md --- md/4_export_embed/dev_embed/export_exe/export_exe.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/md/4_export_embed/dev_embed/export_exe/export_exe.md b/md/4_export_embed/dev_embed/export_exe/export_exe.md index 81b73cb..13ab21a 100644 --- a/md/4_export_embed/dev_embed/export_exe/export_exe.md +++ b/md/4_export_embed/dev_embed/export_exe/export_exe.md @@ -37,7 +37,7 @@ take a look at the CAVEATS below if you are trying to export to OS X and especia - The build for arm/m1-architecture is even harder to run, apple forbids running unsigned apps that are build for arm entirely, not even whitelisting is possible...you may sign it on your own, though. - Once you downloaded the app, USE THE FINDER to move it basically anywhere else (like your desktop) before opening it - Apple puts downloaded apps into a random read-only directory UNTIL YOU MOVE IT USING FINDER, we need to write to the directory...sorry... -- There are ways to still be able to execute the app: (on this website)[https://appuals.com/damaged-app-cannot-be-opened-on-macos-error/] we recomment the command line snipped: `sudo xattr -cr appName.app` +- There are ways to still be able to execute the app: [on this website](https://appuals.com/damaged-app-cannot-be-opened-on-macos-error/) we recomment the command line snipped: `sudo xattr -cr appName.app` ## Export Options