Am 07.06.2012 um 12:02 schrieb Jean-Marc Lasgouttes:
> Le 07/06/2012 11:58, Stephan Witt a écrit :
>> When using a library from /opt/local/lib, e.g. QtCore, you are forced to use
>> the libs used when building QtCore.
>> If QtCore was build with libiconv from /opt/local/bin you have to use this
>> one when linking LyX.
>> But the linker does the implicit lookup only for libraries in /usr/lib.
>>
>> BTW, the resulting LyX (using macports) does not work on a system without
>> macports.
>
> Is there some pkgconfig (*.pc) information in these macports builds? In this
> case, the Qt detection code should be able to know what libraries to link
> against.
Yes.
$ tail /opt/local/lib/pkgconfig/QtCore.pc
Name: Qtcore
Description: Qtcore Library
Version: 4.7.4
Libs: -L${libdir} -lQtCore
Libs.private: -lz -lm -framework ApplicationServices
Cflags: -DQT_SHARED -I/opt/local/include -I${includedir}
$ tail /opt/local/lib/pkgconfig/glib-2.0.pc
Name: GLib
Description: C Utility Library
Version: 2.32.3
Requires.private:
Libs: -L${libdir} -lglib-2.0 -lintl
Libs.private: -lintl -liconv
Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include -I${includedir}
But I'm afraid using pkgconfig results in a LyX with hard macports dependencies.
Stephan
