Skip to content
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

Arm support for pyinstaller #13

Closed
wants to merge 1 commit into from

Conversation

shanemhansen
Copy link

These are bootloader executables for arm as well as the platform
detection code needed to utilize them.
Executables were created using:
./waf configure --no-lsb
./waf install
on an Arm system.

These are bootloader executables for arm as well as the platform
detection code needed to utilize them.
Executables were created using:
./waf configure --no-lsb
./waf install
on an Arm system.
@matysek
Copy link
Member

matysek commented Jun 19, 2012

Could you please provide more information about python version and HW / SW configuration it has been tested with?

Was it really that simple to just update the platform detection code or do you expect more pull requests related to arm platform?

Do you think it is worth to include binary bootloaders for arm platform?

Is there any simulator I could use to try recompile bootloaders for arm?

@shanemhansen
Copy link
Author

Hardware was: http://archlinuxarm.org/platforms/armv5/seagate-goflex-home armv5 (armv5tel)
OS: Linux 3.1.10 (Mostly debian stable packages)
Python version: 2.7.2
gcc: 4.6.2

Prior to this patch on arm systems pyinstaller executes sucessfully, but builds an executable for Linux-32bit (x86). Building the proper bootloaders for arm is actually as simple as running waf configure and waf install, I did have trouble finding a lsbcc package for my system, which is why the executables were built with --no-lsb. waf install puts the arm executables in Linux-32bit, I manually placed them into Linux-32bit-arm, and updated the platform detection code.

I can verify that this setup works with pyinstaller to produce a valid directory-style installation for a relatively complex project (using twistd).

I haven't had much luck with finding an arm simulator that will work. Some posts like this: http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu indicate it's possible.

I found this documentation: http://wiki.samba.org/index.php/Waf which has some nice tips for arm cross compiling.

@matysek
Copy link
Member

matysek commented Aug 24, 2012

Thanks for your testing on arm. Similar change was implemented in c081313 .

I think include binary bootloaders for arm is not suitable. Binary bootloaders make sense only for more widespread platforms.

@matysek matysek closed this Aug 24, 2012
@htgoebel
Copy link
Member

For just compiling the bootloaders, cross-compiling would be a solution. But it's quite some effort setting this up. So I agree we will not supply bootloader.

@shanemhansen: What agout adding your data to the wiiki at www.pyinstaller.org?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants