Graham Dumpleton wrote:
>
> I don't understand the problem, you can say where it installs the
> framework, it doesn't have to be under /Library, so can be in your
> special SDK folder. For example:
>
> ./configure --prefix=/usr/local/python-2.5.4 \
> --enable-framework=/usr/local/python-2.5.4/frameworks \
> --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.5 \
> --with-universal-archs=all
>
> This would put stuff under /usr/local/python-2.5.4.
While that looked promising, Graham, it didn't actually address my needs.
"--with-universal-archs=all" produces binaries for "ppc" and "i386". I need
64-bit binaries (i.e., "x86_64"). Also, after building with your settings,
there are no shared libraries produced. All I get is the static-link library,
"libpython2.5.a", which is what I'm getting with every other configuration as
well.
So, indeed, I now know that I needn't place frameworks into default locations,
but that doesn't really get me any closer to producing a 64-bit Python shared
library. Thanks for trying, though.
--
Render me gone, |||
Bob ^(===)^
---------------------------------oOO--(_)--OOo---------------------------------
"If I owned Hell and Texas, I would rent out Texas and live in Hell."
- General Phil Sheridan
--
http://mail.python.org/mailman/listinfo/python-list
