-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Just a heads up #17
Comments
Well actually i can't run this project either: $ ./build-linux.py
|
Thanks for the project pointers! The |
Cross-linking issues theopolis/build-anywhere#3 It looks like it may be useful to grab some of the recipes from build-anywhere, as a basis for this projects build. @hippylover , to go back to one of your questions, the reason for this project is primarily to build standalone Python as a bundle of bits, so that people can pick and choose which bits they want, and those decisions might be made due to licensing decisions. Just building static Python isnt enough - usually people want it to be redistributable, and that is where it gets difficult. The tarballs at Releases are usually enough for anyone. They got me started, and as a result I never tried fwiw, I have a static Python build setup at https://build.opensuse.org/project/show/home:jayvdb:python37-static , and ctypes wasnt a problem. It is based on static libs which were already avail in openSUSE + some mods because they tend to disable static libs. And on top of that I have Nuitka doing a standalone build at https://build.opensuse.org/package/show/home:jayvdb:storyscript-standalone-static/python-story The key element I needed was a more expansive |
Hi. Thanks for your response. I tried the musl build in Releases -- the glibc one gave me an error in centos 6. tried to install pyqt from pip but all it said was "Killed". I looked at a strace output and -- as far as i am able to comprehend -- it seems it cannot connect to the internet. |
I got the same error
|
Could you please provide more information in the dedicated issue? |
There's a project tackling portable builds on linux called build-anywhere located here: https://github.com/theopolis/build-anywhere
I don't know if it is useful, just thought i should tell. Before i found python-build-standalone project i tried to build the _ctypes extension statically(still can't get it to work) through build-anywhere project.
There's another thing though. Following this: https://wiki.python.org/moin/BuildStatically in addition to build-anywhere i can build a python binary with no deps. I can't get _ctypes to compile though so i can't really test it. But isn't this better than the binary depending on a lot of stuff gotten through this project or am i confused. Maybe those deps are to static builds?
The text was updated successfully, but these errors were encountered: