Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
QB64pe 4.0 on Mac Troubles
#11
I also guess a problem with Xcode. I had the very same error message compiling QB64pe 3.14.1 on my old Mac mini M1 after updating to Sequoia. Version 3.14.0 compiled flawlessly though. As said, on my new M4 everything compiles fine.
Reply
#12
Thank you, @a740g! And thanks, Steve. I’ll try reinstalling XCode. Appreciate the help! +1 to you both.  Smile

(Yesterday, 10:22 AM)Cybermonkey342 Wrote: I also guess a problem with Xcode. I had the very same error message compiling QB64pe 3.14.1 on my old Mac mini M1 after updating to Sequoia. Version 3.14.0 compiled flawlessly though. As said, on my new M4 everything compiles fine.
Thanks, cybermonkey342. I appreciate a monkey helping out this ape!
Reply
#13
Well, I went to uninstall Xcode to start fresh and discovered the app wasn't even there at all. And I had no command line tools either. I love Macs, but sometimes stuff just seems to go poof...

I deleted the Developer folder and reinstalled Xcode and the command line tools. Then a fresh copy of qb64pe 4.0 happily compiled on my system - great! But...

@a740g - Yes, files with spaces in their names won't run and New programs without names won't run. If I open a New window and type in a few lines of code and then hit F5, the IDE only creates a start shell and an exe in the qb folder. If I then name and save that program, close the IDE and relaunch, then pressing F5 will run it. 

Edit: Likewise, copy and pasted files won't run until they're saved and relaunched... And folders can't have spaces in their names either!

Thanks for all your effort, dev team.  Smile
Reply
#14
For the filenames with spaces and such I believe I see the issue, I can get it fixed in the next release. In the mean time you may be able to avoid it by toggling the `Display Logging Output` option in the `Run` menu (a terminal with the logging output will pop-up alongside your program, but you can ignore it if you don't care about the logging output).
Reply
#15
Thanks, @DSMan195276! That works just fine. +1
Reply




Users browsing this thread: 2 Guest(s)