Building BasiliskII on macOS failed #248
Comments
|
@RonaldPR - It builds here on an M2 Mac running macOS 15.2 with SDL2. Did you use the command-line command to build it, as specified on the front page of this project. In the terminal, CD to the MacOSX folder, and then:
That's what always works for me. If you try to build from Xcode itself, you may see problems. And if you used the command line and it failed, try restarting your machine and run it again. |
|
Restarted my machine. Tried again. Same failure. I did what I always do. (The last time in Sonoma and with an earlier Xcode version.) I opened the BasiliskII.xcodeproj in Xcode, changed Deployment Target to the supported minimum, now 11.5 Big Sur, and changed Bundle Identifier to "com.emaculation.basiliskii" (preparing for later notarizing). In Terminal |
|
Very strange! I did exactly the same things that you described and produced this build: Perhaps you didn't exit Xcode? I have no idea why that would affect anything, but it's the only thing I can think of. |
|
Is there a way to get the actual messages output of the compiler that Xcode ran so we don't have to guess what it failed to compile? |
|
What's meant by the readme instruction "On an Intel Mac, the libraries [gmp, mpfr] should be cross-built." |
|
On an arm64 mac, build natively. |
|
No, that's fine, I'm just trying to understand what the build situation on newer macs than what I have access to is |
|
I wondered if I should reinstall gmp and mpfr. But I do not know if I can install the newer latest versions gmp 6.3.0 and mpfr 4.2.1. @emendelson @rakslice |
|
Right, so for posterity some general knowledge about Terminal output of some kind of build. It's a lot of stuff mixed together: the commands that were run, and the output of those commands, which includes errors and warnings, and keeping in mind some of the commands run other commands, such as Sometimes the errors don't have a keyword like |
|
So, to explain that, I can see a |
|
Ah but there's another clue: etc. |
|
I was building in a folder "Laatste Builds". The space also prevented to find the needed file by truncating the paths: make: *** No rule to make target Thanks! ( I seem to be unable to make the code show up correctly here. Hence all the edits.) |
|
Not a big deal, but I wonder if the possibility of spaces in paths could be accounted for in the source code. |
|
Yeah I consider it a legitimate problem if the scripts don't work in a directory with spaces, maybe not one to spend an unlimited amount of time on, but worth me looking into at some point, because it's often not very difficult to solve. Re formatting: Tools like to use backquotes as left-quotes like in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tried building BasiliskII from latest source.
M1 iMac - MacOS Sequoia 15.2 - Xcode 16.2 - DSL2 2.30.11
Build failed
The following build commands failed:
PhaseScriptExecution Run\ Script /Users/ronald/Desktop/Laatste\ builds/macemu-master/BasiliskII/src/MacOSX/build/uae_cpu_2021.build/Release/uae_cpu_arm64.build/Script-E4FC27492642C2E600C64E21.sh (in target 'uae_cpu_arm64' from project 'uae_cpu_2021')
(1 failure)
ronald@MacKanjer6 MacOSX %
The text was updated successfully, but these errors were encountered: