Dear Lawrence, Thank you for good pointing out. Now I'm afraid that there is a possibility that setting both of PKG_CONFIG_SYSROOT_DIR & PKG_CONFIG_LIBDIR made pkg-config search wrong directory. Something like this.
PKG_CONFIG_SYSROOT_DIR=/sysroot/cross-blahblahblah -> pkg-config will search /sysroot/cross-blahblahblah/usr/lib/pkgconfig/ PKG_CONFIG_LIBDIR=/sysroot/cross-blahblahblah/usr/lib/pkgconfig/ -> pkg-config will search /sysroot/cross-blahblahblah/usr/lib/pkgconfig/ PKG_CONFIG_SYSROOT_DIR=/sysroot/cross-blahblahblah PKG_CONFIG_LIBDIR=/sysroot/cross-blahblahblah/usr/lib/pkgconfig/ -> pkg-config will search /sysroot/cross-blahblahblah/sysroot/cross-blahblahblah/usr/lib/pkgconfig/ -- Nik, if you set PKG_CONFIG_DEBUG_SPEW and execute pkg-config, you would receive some messages telling where freetype2.pc comes from, like this. ... Looking for package 'freetype2' Looking for package 'freetype2-uninstalled' Reading 'freetype2' from file '/usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc' Parsing package file '/usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc' line>prefix=/usr ... Please confirm which freetype2.pc is used. Regards, mpsuzuki Lawrence D'Oliveiro wrote: > On Sun, 6 Nov 2016 07:22:35 +0100, Nikolaus Neusser wrote: > >> All i know is, that the developer of the plugin told >> me, that freetype2 is found through pkg-config. > > According to the man page <https://linux.die.net/man/1/pkg-config>, you > have to set the PKG_CONFIG_SYSROOT_DIR environment variable to point to > where the includes and libs for the target system are kept, in order to > do cross-compilation. > > _______________________________________________ > Freetype mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/freetype > _______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
