-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails on macOS 10.14 (Mojave) #92
Comments
Does the |
Some more information. Your error stack contains
indicated that the variable The code I am looking at however (https://github.com/andreas-kupries/critcl/blob/master/lib/critcl/Config#L97) checks for the empty string and prevent the Ah! That was issue #84, and the change is not in a release yet. What happens on your system when you put that change in ? Right now I suspect that while the stack trace goes away SDKROOT still has to be set manually to make it work. Not sure, I do not have a Mojave system to test with. |
I did not have this issue with Mac OS 14.6 but I have been tinkering with the Config in order to use Apple Silicon (arm64) compilation.
This Technical Note (TN2339) from Apple says that https://developer.apple.com/library/archive/technotes/tn2339/_index.html The 10.9 release was codenamed Mavericks and released in 2013.
Yes it looks that way. |
The build of Critcl using the standard instructions fails on macOS 10.14. It turns out the reason is that the detection of the SDK path does not work on new versions of macOS and Xcode. Defining the SDKROOT environment variable fixes the problem but the code should be fixed to automatically detect the SDK path.
Here is the failure:
Here is the new way to identify the SDK path:
And here it is working after defining the SDKROOT variable. Ideally, the build script would automatically run the above command, get the right path and build correctly.
The text was updated successfully, but these errors were encountered: