+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3)
+---- Forum: Help Me! (https://qb64phoenix.com/forum/forumdisplay.php?fid=10)
+---- Thread: Compiling for Mac-OS (/showthread.php?tid=2518)
Pages:
1
2
RE: Compiling for Mac-OS - NakedApe - 03-13-2024
(03-13-2024, 04:55 PM)mdijkens Wrote:You're welcome, mdijkens. I tried yr program on a newer Mac mini M2 and the zip opened right up with no issues. Double clicking on the mdAnswerIntents_start.command icon launched the program immediately. To unzip yr folder the second time I used "RAR Extractor - Unarchiver Pro." I've had good luck with that app. Using the .command file to start a MacOS program is best practice since it's a mini batch file that cleans up after itself, closing the terminal app for yr program upon termination.(03-13-2024, 04:40 PM)NakedApe Wrote: Howdy. I tried expanding the zip file, but the unArchiver said the contents were corrupted. On the second try it worked with complaints from the utility... The program ran on my Mac asking for the security token. I'm running it on an M1 Mac with Sonoma 14.2.1. Good luck with it.This is great news! (well not that it was corrupt zip first time) THANKS TED
Ted
Basically means you got it running!
Did you have to do something with the application before you could run it? Then I can create a readme.txt for dummies
Is there a better/safer way to zip/archive this on mac? I only found in Finder > right mouseclick > compress
Do I also need to include the .command file?
Really like to get this sorted robust for future also
EDIT: Of course before any downloaded QB64PE program will run, you have to jump through the security hoops: System Settings > Privacy and Security > scroll to the bottom and allow the .command and the .exe files to be run...
RE: Compiling for Mac-OS - mdijkens - 03-13-2024
(03-13-2024, 06:38 PM)NakedApe Wrote: You're welcome, mdijkens. I tried yr program on a newer Mac mini M2 and the zip opened right up with no issues. Double clicking on the mdAnswerIntents_start.command icon launched the program immediately. To unzip yr folder the second time I used "RAR Extractor - Unarchiver Pro." I've had good luck with that app. Using the .command file to start a MacOS program is best practice since it's a mini batch file that cleans up after itself, closing the terminal app for yr program upon termination.Thank you for this additional info
I understand that from my side I don't have to do anything different then what I already did.
Quote:EDIT: Of course before any downloaded QB64PE program will run, you have to jump through the security hoops: System Settings > Privacy and Security > scroll to the bottom and allow the .command and the .exe files to be run...Is this done for all (future) .command and applications, or is that done per application?
I think customers would normally prefer the latter
RE: Compiling for Mac-OS - NakedApe - 03-13-2024
(03-13-2024, 09:42 PM)mdijkens Wrote:Every unrecognized executable (including .command files) needs permission to run in my experience, but I'm no expert. I'm glad it worked out for you.(03-13-2024, 06:38 PM)NakedApe Wrote: You're welcome, mdijkens. I tried yr program on a newer Mac mini M2 and the zip opened right up with no issues. Double clicking on the mdAnswerIntents_start.command icon launched the program immediately. To unzip yr folder the second time I used "RAR Extractor - Unarchiver Pro." I've had good luck with that app. Using the .command file to start a MacOS program is best practice since it's a mini batch file that cleans up after itself, closing the terminal app for yr program upon termination.Thank you for this additional info
I understand that from my side I don't have to do anything different then what I already did.
Quote:EDIT: Of course before any downloaded QB64PE program will run, you have to jump through the security hoops: System Settings > Privacy and Security > scroll to the bottom and allow the .command and the .exe files to be run...Is this done for all (future) .command and applications, or is that done per application?
I think customers would normally prefer the latter