On Mon, Mar 11, 2019 at 10:25:59PM -0400, Jon Ringle wrote: > In rules/qt4.make, there is: > ``` > ifdef PTXCONF_QT4_EXAMPLES > QT4_DEVPKG := NO > endif > ``` > This means that a qt4 dev package will be probably be created. > The qt4.extract rule will create some mkspecs files that contain the > absolute path for include and lib dirs. These mkspecs files get packaged up > in the qt4-*-dev.tar.gz package and does not get fixed up. This caused some > very strange errors when building our project because the include path that > the project used picked up the include path from the qt4 dev package and > pointed to the wrong header file from another platform.
Huh, I expect that qt5 has the same problem. > Having a qt4 dev package is a real build time saver and I don't really want > to mark it with QT4_DEVPKG := NO unconditionally, but I'm not sure what the > proper fix for it would be. Take a look at what e.g. rules/host-autotools-autoconf.make does. You need to overwrite qt4.install.post and then do some s/old-sysroot/new-sysroot/ before calling world/install.post. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list [email protected]
