Re: Preventing usage of broken 3rd party libxml.framework install
Re: Preventing usage of broken 3rd party libxml.framework install
- Subject: Re: Preventing usage of broken 3rd party libxml.framework install
- From: Jeffrey Wilson <email@hidden>
- Date: Thu, 20 Dec 2007 10:38:24 -0500
On Dec 20, 2007, at 9:36 AM, Jean-Daniel Dupas wrote:
Le 20 déc. 07 à 15:07, Jeffrey Wilson a écrit :
Some software installed a (development-wise) broken
libxml.framework in /Library/Frameworks that takes in Xcode
precedence over the /usr/include/libxml2 headers. (It has it's
own /Headers directory that is not a symlink to /Versions/xxx/
Headers and is missing cruical headers).
How do I force a include file order?
I'd prefer to adjust my projects once instead of finding out how
that broken framework made it into my /Library/Frameworks folder
and try to catch up with broken reinstalls over a manually fixed
version.
You could forego the use of the libxml.framework and just link
against the /usr/include/libxml2. Add -lxml2 to your "Other Linker
Flags" and make sure you "Header Search Paths" starts with
something like "$(SDKROOT)/usr/include/libxml2". I do this for an
OSS project.
Wrong, you header search path must not include $(SDKROOT).
Xcode take care of this for you. Xcode include the $(SDKROOT) part
before each include path if the path exists in the target SDK.
Why *must* I *not* use $(SDKROOT)/usr/include/libxml2? Is there any
particular harm in explicitly asking for this path?
Anyhow, having /usr/include/libxml2 at the start of the header search
path should force that to be used, right?
Jeff _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden