ok, i did the following:
  - export all variables like before including setting PKG_CONFIG_DEBUG_SPEW
  - i ran on the host: pkg-config --modversion freetype2
  -> Output, see below:

Note:
An interesting thing i just noticed is: When i run qmake (having set PKG_CONFIG_DEBUG_SPEW) i don't get any debug messages like when manually running pkg-config.
Only the error message: Project ERROR: freetype2 development package not found
Could this maybe mean, that qmake is not calling pkg-config?

Output for: "pkg-config --modversion freetype2"

   /Looking for package 'freetype2'//
   //Looking for package 'freetype2-uninstalled'//
   //Reading 'freetype2' from file
   
'/home/niki/opt_qt_for_rpi/qt5.6.1-1/sysroot/usr/lib/arm-linux-gnueabihf/pkgconfig/freetype2.pc'//
   //Parsing package file
   
'/home/niki/opt_qt_for_rpi/qt5.6.1-1/sysroot/usr/lib/arm-linux-gnueabihf/pkgconfig/freetype2.pc'//
   //  line>prefix=/usr//
   // Variable declaration, 'prefix' has value '/usr'//
   //  line>exec_prefix=/usr//
   // Variable declaration, 'exec_prefix' has value '/usr'//
   //  line>libdir=/usr/lib/arm-linux-gnueabihf//
   // Variable declaration, 'libdir' has value '/usr/lib/arm-linux-gnueabihf'//
   //  line>includedir=/usr/include/freetype2//
   // Variable declaration, 'includedir' has value '/usr/include/freetype2'//
   //  line>//
   //  line>Name: FreeType 2//
   //  line>URL: http://freetype.org//
   //  line>Description: A free, high-quality, and portable font engine.//
   //  line>Version: 18.0.12//
   //  line>Requires://
   //  line>Requires.private: //
   //  line>Libs: -L${libdir} -lfreetype//
   //  line>Libs.private: -lz -lpng12 -lz -lm//
   //Unknown keyword 'Libs.private' in
   
'/home/niki/opt_qt_for_rpi/qt5.6.1-1/sysroot/usr/lib/arm-linux-gnueabihf/pkgconfig/freetype2.pc'//
   //  line>Cflags: -I${includedir}//
   //Path position of 'freetype2' is 2//
   //Adding 'freetype2' to list of known packages//
   //18.0.12/






Am 06.11.2016 um 09:11 schrieb suzuki toshiya:
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
Freetype@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype



_______________________________________________
Freetype mailing list
Freetype@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype

Reply via email to