We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When building the objective C files during the VM build, cmake by default tried to use the MacOS12 SDK, failing compilation.
We worked it around by explicitly setting -DCMAKE_OSX_SYSROOT=... as specified here: https://stackoverflow.com/questions/10165335/can-cmake-specify-the-base-sdk-on-mac-os-x.
We also saw that CMake provides already support to detect the SDK and that we should use https://cmake.org/cmake/help/latest/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html#variable:CMAKE_OSX_DEPLOYMENT_TARGET to specify the target instead of setting the compiler flag manually like this
pharo-vm/CMakeLists.txt
Line 263 in 48ddfee
Otherwise CMake can override it and provoke this issue
The text was updated successfully, but these errors were encountered:
@RenaudFondeur I fixed this in the last PR, would you mind if this works out of the box in your machine?
Sorry, something went wrong.
(you will need to pull)
Successfully merging a pull request may close this issue.
When building the objective C files during the VM build, cmake by default tried to use the MacOS12 SDK, failing compilation.
We worked it around by explicitly setting -DCMAKE_OSX_SYSROOT=... as specified here: https://stackoverflow.com/questions/10165335/can-cmake-specify-the-base-sdk-on-mac-os-x.
We also saw that CMake provides already support to detect the SDK and that we should use https://cmake.org/cmake/help/latest/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html#variable:CMAKE_OSX_DEPLOYMENT_TARGET
to specify the target instead of setting the compiler flag manually like this
pharo-vm/CMakeLists.txt
Line 263 in 48ddfee
Otherwise CMake can override it and provoke this issue
The text was updated successfully, but these errors were encountered: