Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Easiest is to remove/hide the pkg-config utitily, so that configure
doesn't even have a chance of detecing those "alien" libraries.

Well, configure looks for libxml2 by running xml2-config, not pkg-config. (Check the use of 
PKG_CHECK_MODULES_MACHACK , from acinclude.m4.)

And at least on 10.6.7 with Xcode3 *and* Xcode4 installed, there is a /usr/bin/xml2-config, which 
gets used, and not the one that would correspond to the SDK we want to build with, which at least 
for me also comes with an xml2-config, in /Developer/SDKs/MacOSX10.4u.sdk/usr/bin/xml2-config .

Not that things would be all good if /Developer/SDKs/MacOSX10.4u.sdk/usr/bin/xml2-config --cflags 
was run instead either; for some obscure reason that *still* outputs -I/usr/include/libxml2, 
instead of what it presumably actually means, 
-I/Developer/SDKs/MacOSX10.4u.sdk/usr/include/libxml2. Go figure. Seems like whoever ported libxml2 
to the 10.4 SDK didn't bother making the xml2-config script actually adapt to where the 10.4 SDK is 
installed, but it hardcodes the installation location -relative /usr path as if it was absolute. Or 
whatever.

And still another point is that we hardcode this /Developer/SDKs/MacOSX10.4u.sdk path a couple of 
times in the configure.in, but surely that software package can be installed in some other 
location, too... Is there any way to find out the actual installation root of the 10.4 SDK?

--tml



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.