Toolchain build kivy command is failing with Xcode 16 #936
Comments
lukieh2014
changed the title
|
Hello, I have the same problem on the MacBook Air M2. MacOS 15.0 Can no longer perform a toolchain build process. Is there already a solution for this? Best regards |
|
I am seeing the same issue. It looks like it is occuring in the libffi recipe build. |
|
Additional errors I am seeing in the libffi config.log |
|
Applying this patch fixes the libffi build: And now |
|
I have the same build problems including identical messages listed previously by others. Using:
|
|
I am working on a patch. It is important to note that homebrew can pollute the python search path, so make sure you remove |
|
For those wanting to try my patch: Then to build: |
|
https://www.xcodes.app/ |
This is working for me! the toolchain built successfully, thanks so much ! |
|
Hello, I haven't been able to test it yet. Does the fix also work on macos 15.0? |
It looks like my pull request was accepted and merged into main. It was passing all of the tests on their ci system, so it should be backward compatible. My change removes a flag that was already deprecated. It also suppresses a new compiler warning. |
|
Thank you! I will check... |
I just did a clean: and it built completely for me. |
|
Could it be that we have different errors? |
Per the guide, I used Homebrew to install pkg-config, libtool, autoconf, and automake. If I remove opt/homebrew/bin from PATH, the toolchain build complains that those items aren't installed. I am new to Mac development... what am I doing wrong? Is there an alternative way to install and reference those dependencies for the toolchain build? I've only used Homebrew to install those 4 packages. I use the CLT supplied Python with venv and I don't use Homebrew to install/manage Python in any way. In this case, will Homebrew still pollute the Python search path? In my case, when I put opt/homebrew/bin back in PATH, the newly merged main seems to work fine. I'm confused. |
|
Hi @eljarro There is something going on with the homebrew python packages interfering with kivy-ios. If keeping homebrew in your path is needed, than I suggest doing it. However, it has been found more than once that this may be necessary (#929, #905, #901) since this package causes strange build errors. This is even more confusing since kivy-ios builds So there are 3 different python versions at play. I personally create my virtual environment using In the end, I suggest doing what works for you. |
|
1) So is it correct to assume that Homebrew can stay in $PATH as long as Homebrew is NOT used to install Python(s)?
2) If Homebrew path is removed from $PATH, how does “toolchain build python3 kivy” process know where to find the required non-Python dependencies like autoconf, automake, etc?
Much appreciated.
…Sent from my iPad
On Sep 25, 2024, at 6:23 PM, Juan Sanchez ***@***.***> wrote:
Hi @eljarro<https://github.com/eljarro>
There is something going on with the homebrew python packages interfering with kivy-ios. If keeping homebrew in your path is needed, than I suggest doing it. However, it has been found more than once that this may be necessary (#929<#929>, #905<#905>, #901<#901>)
/opt/homebrew/bin/brew uninstall --ignore-dependencies libb2
since this package causes strange build errors. This is even more confusing since kivy-ios builds python (for iOS?) and hostpython (for macOS?).
So there are 3 different python versions at play. I personally create my virtual environment using /usr/bin/python3 instead of the one from homebrew.
In the end, I suggest doing what works for you.
—
Reply to this email directly, view it on GitHub<#936 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCFJNKNULF3UDDDF7CVRTV3ZYNO2JAVCNFSM6AAAAABOY6Y3MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZVGU2TENZZGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I'm thinking that brew may be needed in your path for some packages. I think that
I think I got confused, since some packages are not rebuild do to caching, so brew is probably needed. My impression is that the or run directly as is: Apparently only the only recipe I see calling an autotool is libzbar: The famous So I have been wrong about not needing homebrew in your path. |
|
Fixed by #937 |
Versions
The 'toolchain build kivy' command does not seem to work with Xcode 16, producing errors shown below.
To Reproduce
cd kivy_project
python3.11 -m venv venv
. venv/bin/activate
pip install kivy-ios
toolchain build kivy <- causing errors
I have also tried it with cloning the github, and get the same errors:
Expected behavior
A successful build with toolchain.
Logs
Additional context
I am on Apple silicon M3 mac, I managed to get a successful build with Xcode 15.2 (after doing brew uninstall libb2), however I don't think that xcode15.2 supports my current IOS version (17.7). After upgrading to Xcode16 (and doing clean runs each time i.e. deleting dist, .cache, build, making new venv, toolchain distclean etc) I am getting the errors above. I think it may be due to the IOS SDK being used (with Xcode16 it is IOS 18) is too new and is unsupported? but not really sure - i am a bit of a noob with this stuff...
The text was updated successfully, but these errors were encountered: