--build-base and install
I'm trying to build and install pysqlite-1.1.6 using --build-base, because I want the files created during the build to be placed in a specific directory outside the source directory. --build-base works just fine with the 'build' command, but not at all with the 'install' command. How is 'install' supposed to find the files that 'build' placed elsewhere? Is the lack of --build-base support a problem with pysqlite's setup.py script or a more fundamental problem with distutils? Or am I just being dense? FTR: Python 2.4.1 Thanks, -Barry
On 6/30/05, Barry Warsaw
I'm trying to build and install pysqlite-1.1.6 using --build-base, because I want the files created during the build to be placed in a specific directory outside the source directory.
--build-base works just fine with the 'build' command, but not at all with the 'install' command. How is 'install' supposed to find the files that 'build' placed elsewhere? Is the lack of --build-base support a problem with pysqlite's setup.py script or a more fundamental problem with distutils? Or am I just being dense?
FTR: Python 2.4.1
Have you tried python setup.py build --build-base=whatever install ? I chain the commands like this to switch compilers on Windows (build --compiler=mingw32 bdist_wininst) and it works fine for that. Paul.
On Thu, 2005-06-30 at 10:01, Paul Moore wrote:
Have you tried
python setup.py build --build-base=whatever install
?
I chain the commands like this to switch compilers on Windows (build --compiler=mingw32 bdist_wininst) and it works fine for that.
Thanks Paul, that does work perfectly. I didn't realize you could chain commands like that! -Barry
Barry Warsaw
On Thu, 2005-06-30 at 10:01, Paul Moore wrote:
Have you tried
python setup.py build --build-base=whatever install
?
I chain the commands like this to switch compilers on Windows (build --compiler=mingw32 bdist_wininst) and it works fine for that.
Thanks Paul, that does work perfectly. I didn't realize you could chain commands like that!
Another way is to write a setup.cfg file - that way you could not forget to specify the flags all the time. Thomas
Barry Warsaw wrote:
On Thu, 2005-06-30 at 10:01, Paul Moore wrote:
Have you tried
python setup.py build --build-base=whatever install
?
I chain the commands like this to switch compilers on Windows (build --compiler=mingw32 bdist_wininst) and it works fine for that.
Thanks Paul, that does work perfectly. I didn't realize you could chain commands like that!
Aside: you can also put these options into the setup.cfg file, so that you don't have to retype them every time. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 30 2005)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
At 04:49 PM 6/30/2005 +0200, M.-A. Lemburg wrote:
Barry Warsaw wrote:
On Thu, 2005-06-30 at 10:01, Paul Moore wrote:
Have you tried
python setup.py build --build-base=whatever install
?
I chain the commands like this to switch compilers on Windows (build --compiler=mingw32 bdist_wininst) and it works fine for that.
Thanks Paul, that does work perfectly. I didn't realize you could chain commands like that!
Aside: you can also put these options into the setup.cfg file, so that you don't have to retype them every time.
Not only that, if you want to always select a particular compiler, you can put it in your $HOME/pydistutils.cfg (Windows) or ~/.pydistutils.cfg (Unixes), or in a distutils.cfg file in the package directory for distutils (any platform). I do this for any new Python install on Windows, and never have to use the --compiler or -c option.
participants (5)
-
Barry Warsaw -
M.-A. Lemburg -
Paul Moore -
Phillip J. Eby -
Thomas Heller