-
Notifications
You must be signed in to change notification settings - Fork 35
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
failed to build under android (termux) #223
Comments
It's been about three months and I'm experiencing the same issue here. Any progress on a fix? Error log is included in the link I sent. |
I have no experience with building for Android (and don't own an Android device). Happy to take help. :) |
Are there any platform tags that would enable the distribution of a wheel working for termux ? Or should it be systematically build from source ? Now since I don't yet have a clear vision on how to scale a solution that would avoid having to implement per-package hacks ... Footnotes |
You can't distribute wheels for termux. So it would be a source build. The problem is the source build is broken on that platform. We should provide a way to package CMake using a system CMake, but that's a specialized situation, as you can't control the CMake version. A user should be able to set a minimum version of CMake in pyproject.toml and have it respected. #227 - actually, if that was implemented and tmux was okay to distribute the python package too, that might work fairly well (though you'd still need to build without isolation). For this specific case, the "immediate" solution would be to simply add a platform tag to avoid the |
You could try out BlissOS or something in a VM or a spare drive/partition, but I suspect the issue would not be present on an x86 Android installation. |
I expect it would be if they are QEMU emulated (don’t know if they are). But yes, likely right if they are actually a rebuild for x86. |
@henryiii this appears to be a general problem on arm based machines. People are experiencing the same issue on arm64: rapidfuzz/RapidFuzz#215 and armv7: rapidfuzz/RapidFuzz#223. |
I am running into similar problems with the ninja package. So for now I will use:
and require the user to have cmake installed on the system for arm machines. |
Hello experts, I am trying to install |
Hi there experts, I was able to get But cmake still sucks. Any suggestions would be much appreciated. Someone mentioned to pass on some flags to resolve it. Is it possible for someone to look into this. Error line:
Details:
Thanks. |
Installing cmake from source requires cmake to be available. For this reason it only makes sense to install this package if a wheel is available or a newer cmake version than the one available on the system is needed. In my packages I started test for a system version of ninja/make and cmake at build time using an in-tree build backend. See here: rapidfuzz/Levenshtein@30b51bd. This way e.g. in termux users can simply install cmake from the package manager. I think it would make sense for |
Thanks for suggestions @maxbachmann.
I would link this comment on here. |
At the details section of #223 (comment) I am trying to install opencv-python at termux and it seems to also install cmake for python |
Any progress so far? I'm having the same error: |
The path forward here is what is done in scikit-build-core, you can check for CMake and not install it if it's present via PEP 517 build hooks. In fact, you can include scikit-build-core and use the |
(It will take longer to finish scikit-build-core and move scikit-build over to it) |
You will need to build both cmake and ninja from source. Once they have been built, scipy then has to be built from source (in order to use qiskit). Normal pip install scipy will build the wheel and show it is installed, but won't import. After that qiskit installs just fine. For qiskit_aer, you also need to build from source. |
I have run into it yet again AD 2024 - a kind of deja vu. Ugly solution:
Locate where the missing file is:
2a. Change it in the .h files:
or 2b. Add into CMakeLists.txt in the same directory as the libarchive source: or
for which see my remark here: |
PS. See also: https://gitlab.kitware.com/cmake/cmake/-/issues/21399 - supposedly a perennial problem. |
rapidfuzz/RapidFuzz#195
The text was updated successfully, but these errors were encountered: