[ python-Feature Requests-848910 ] Enable crosscompilation

SourceForge.net noreply at sourceforge.net
Tue Nov 25 07:55:24 EST 2003


Feature Requests item #848910, was opened at 2003-11-25 13:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=848910&group_id=5470

Category: Build
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jörg Hoh (hohjg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Enable crosscompilation

Initial Comment:
 
Python is awful to crosscompile. I've done it with the help of that 
site ( 
http://www.ailis.de/~k/knowledge/crosscompiling/python.php), but 
I still had to patch the setup.py myself. 
 
The wish: 
 
Could you avoid to add the standard include path (usually 
/usr/include) to the include paths (in setup.py)? It confuses my 
crosscompiler (for which /usr/include isn't applicable, because it 
produces code for a different plattform and endianess), because 
the includes given by commandline to the gcc are searched 
before the standard include paths. And if there are files with the 
wished names, it will produce lots of errors and warnings. 
 
The second one (a more longterm wish) 
 
Could you split the build process into 2 parts? A part which is 
plattform independet (the (cross-) compilation of the python-binary 
and all required binary libraries), and a plattform specific one, 
which is then running on the target plattform. 
This would help me and other people crosscompiling python for 
more plattforms and embedded systems, which haven't an 
available native compiler (or the plattform isn't suppossed to run a 
compiler because of its limited ressouces). 
 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=848910&group_id=5470



More information about the Python-bugs-list mailing list