You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[DEBUG ] ld: building for 'iOS', but linking in dylib (/opt/homebrew/Cellar/libb2/0.98.1/lib/libb2.1.dylib) built for 'macOS'
[DEBUG ] ld: building for 'iOS', but linking in dylib (/opt/homebrew/Cellar/libb2/0.98.1/lib/libb2.1.dylib) built for 'macOS'
[DEBUG ] ld: unknown options: -miphoneos-version-min=9.0 -miphoneos-version-min=9.0 -I/Users/jack/Desktop/KivyBuilds/dist/include/iphoneos-arm64/ffi -I/Users/jack/Desktop/KivyBuilds/dist/include/iphoneos-arm64/openssl -I/Users/jack/Desktop/KivyBuilds/dist/include/iphoneos-arm64 --sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.4.sdk
[DEBUG ] clang: error: linker command failed with exit code 1 (use -v to see invocation)
[DEBUG ] clang: error: linker command failed with exit code 1 (use -v to see invocation)
Additional context
The configure script for target python uses pkg-config to find an install of libb2. Unfortunately, it finds the macOS one:
Describe the bug
As discussed in s #929 #905 #901,
libb2
needs to be removed, otherwisekivy
fails to build. Specifically, it is the target pythons that are failing.To Reproduce
Most homebrew installations have
libb2
installed. When kivy iOS build fails, removing the package fixes the problem:Expected behavior
kivy iOS should build without error.
Logs
From #901
Additional context
The
configure
script for target python usespkg-config
to find an install oflibb2
. Unfortunately, it finds the macOS one:A patch file should be created so that the recipe for
python3
so theconfigure
script does not check forlibb2
.The text was updated successfully, but these errors were encountered: