[Pythonmac-SIG] Build/install framework Python in non-standard location
Bob Ippolito
bob at redivi.com
Mon Oct 16 18:18:06 CEST 2006
On 10/16/06, Kevin Walzer <kw at kevin-walzer.com> wrote:
>
> I'm trying to build a framework Python 2.5 that installs to a
> non-standard location (/usr/local/python-unix-framework). The reason I'm
> doing this is to link to an X11-based version of Tcl/Tk, and still be
> able to use py2app for app deployment. (I have previously been able to
> build a standard non-framework Python that links to an X11-based Tcl/Tk,
> but the resulting binaries cannot be wrapped via py2app, and the other
> wrapping tools--freeze, cx_freeze, pyinstaller--don't work well or at
> all on OS X.)
>
> I thought that using these build flags would work:
>
> ./configure --enable-framework --enable-universalsdk
> - --prefix=/usr/local/python-unix-framework
>
> Everything built fine, but when I ran sudo make install, everything
> started getting placed in /Library/Frameworks. This isn't what I
> wanted--that's where the official build of Python 2.5 from python.org is
> installed (and which links to Tcl/Tk Aqua). I need the second
> installation to test the X11 version of my application, and the official
> installation to test the Aqua version.
>
> What do I need to hack to get the frameworks to install in my preferred
> location, instead of the default? And why doesn't Python pick up the
> ./configure flags correctly anyway?
It does pick up the configure flags correctly, but you need to pass
the correct configure flags.
If you'd have used --help you'd have seen that --enable-framework
takes a path, which defaults to /Library/Frameworks. If you want it to
go somewhere else, give it a different path.
-bob
More information about the Pythonmac-SIG
mailing list