robert,
Foundation is its own framework (see /System/Library/Frameworks)
yup.
which is implicitly linked in by Cocoa and Carbon.
sigh. more to learn. =-)
clearly time to unpack & actually read my new copy of Hillegass' book ...
which, iiuc, would suggest no dependence whatsoever on libxml -- eithe
hi robert,
*something's* expecting libxml2 to be there ...
I'll bet that it's either Cocoa or Carbon. In that case, you definitely
*don't* want it to use your own libxml2.
makes possible sense in that there's a reference to 'Foundation', which given
your suspicion, refers to the OSX FoundationClas
hi bob,
no matter what i do, the build links against the 'native'
/usr/lib/libxml* ... successful w/ no error, just the 'wrong' lib.
Neither Python itself, nor any extension in the standard library, links to
libxml.
well, that's good -- & at least consistent with why there's no significant
refer
hi all,
i've originally posted this on python-list -- but I have a suspicion my
questions may have to do with Mac-specific issues, so I'll try here as well ...
i've successfully built Python-2.4.1 from src on OSX 10.3.8 as a framework
install with, simply:
./configure \
--enable-framework
hi bob,
then why offer the --prefix arg in the first place? just for
NON-framework installs?
Yes, --prefix is for non-framework installs. If you read the docs for
frameworks, you'll see that it's only "lightly tested" with an alternate
path. You may have more luck if you just use the defaults.
hi bob,
any suggestions as to what's broken here?
Works here, with 2.4.1c1 anyway.
but there have been no relevant changes that I know of.
i dropeed back and tried it with c1 as well ... same prob 4 me.
argh
Most of the arguments you specify to configure are already
on by default or have no effec
Hi all,
i'm building a local instance of Python v2.4.1c2 on a 'virgin install' of
fully-updated OSX 10.3.8. w/ XCode 1.5
'configure' is successful w/
./configure \
--with-prefix=/usr/local/pythontest \
--enable-framework=/usr/local/pythonframe \
--with-threads \
