Open yaitskov opened 3 years ago
Another miner issue but also related to version detection. Output directory contains another sdk version not equal to 10.12 nor 10.13 but 10.6!:
clang -Wno-unused-argument -I/nix/store/096xl1vmxg7hn19pj8s624rpc7h4gdyp-python3-3.9.4/include/python3.9\
-c Modules/_Foundation_inlines.m -o build/temp.macosx-10.6-x86_64-3.9/Modules/_Foundation_inlines.o
It doesn't break anything but looks weird. It must be in sync with version used for building. I was not able to grep location where -o <path>
is generate to trace further.
When I run python3 setup.py build
without nix I get a correct version of sdk there.
So this is unlikely a pyobjc bug.
Oh my workaround is working only for pyobjc-framework-Cocoa module but not for pobjc-core :(
I marked this as stale due to inactivity. → More info
Hi,
I am trying to build pyobjc binding. A builder detects 10.15 but clang gets header files for 10.12, because new protocols are used from 10.13 - build fails.
-isysroot
is ignored by clang (don't no why), but it affects sdk version detection! my workaround is to specify -isysroot a fake path with 10.12 instead of 10.15.I run Big Sur VM on AWS.
default.nix file:
protocol NSItemProviderWriting appears in SDK 10.13 but headers are for 10.12.