building python for multiple targets
hgg9140 at cola.ca.boeing.com
Thu Mar 15 19:56:56 CET 2001
My expreience is with moving site-packages around. Apparently when
you move dirtrees, the .py's work and the .so's work, but the .pyc's
do not. So you may have to delete those and re-byte-compile them in
the new location.
Perhaps someone else can explain why.
Bruce Edge <bedge at troikanetworks.com> writes:
> Just a followup,
> Is it possible to build python to be relacatable?
> So the same runtime tree can be placed in /usr/local/python, or in
> Bruce Edge wrote:
> > I need to build Python for multiple targets from one host.
> > One target is the host, the other is for embedded Linux, with it's own
> > compiler, libs, include, etc, all of which are installed in say
> > /usr/local/rtlinux/...
> > The host build is simple, ./configure, make, make install.
> > The target one is ugly, currently I'd doing:
> > ./configure --include=<rtpath> --bindir=/usr/local/rtlinux/bin
> > --sbindir=</usr/local/rtlinux/sbin ....<every other damn ./configure
> > option there is>
> > Is there a better way?
Harry George E-mail: harry.g.george at boeing.com
The Boeing Company Renton: (425) 237-6915
P. O. Box 3707 02-CA Everett: (425) 266-3868
Seattle, WA 98124-2207 Page: (425) 631-8803
More information about the Python-list