[Distutils] Re: Mixing pure python and extension module and multi platform
Berthold Höllmann
bhoel@web.de
Fri Mar 21 16:59:02 2003
"M.-A. Lemburg" <mal@lemburg.com> writes:
> Berthold Höllmann wrote:
> >>No, because 'pork.pork' is not allowed in py_modules (it's a hack
> >>that sometimes works, but not intended as feature AFAIK).
> > But even this changes do not cure the problem:
> >
> >>cat setup.py ; python setup.py -n install
>
> As I wrote before: you have to explicitly *tell* distutils to
> install in two different directories !
>
> vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
>
> --install-base base installation directory (instead of --prefix o=
r --
> home)
> --install-platbase base installation directory for platform-specific =
files
> (instead of --exec-prefix or --home)
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sorry, but I still understand why. My Python/distutil installation has
the default --install-base as --prefix which is already different from
--install-platbase, or --exec-prefix. If I install a pure Python
module or package it gets installed into "--prefix" which is
"/usr/local/fitools/sandbox/lib/python2.2/site-packages" and packages
holding extension modules get installed into "--exec-prefix" which is
"/usr/local/fitools/sandbox/linux/lib/python2.2/site-packages". Why
doesn't it work when I use both in one "setup" command? Default values
for "--prefix" and "--exec-prefix" are taken from the initial
"./configure" in the python source tree, arent they?
Regards
Berthold
--
bhoel@web.de / http://starship.python.net/crew/bhoel/
It is unlawful to use this email address for unsolicited ads
(USC Title 47 Sec.227). I will assess a US$500 charge for
reviewing and deleting each unsolicited ad.