* [ptxdist] qt4.make leaks include/lib path in devpkg
@ 2019-03-12 2:25 Jon Ringle
2019-03-13 8:18 ` Michael Olbrich
0 siblings, 1 reply; 2+ messages in thread
From: Jon Ringle @ 2019-03-12 2:25 UTC (permalink / raw)
To: ptxdist
[-- Attachment #1.1: Type: text/plain, Size: 776 bytes --]
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.
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.
Thanks,
-Jon
[-- Attachment #1.2: Type: text/html, Size: 983 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ptxdist] qt4.make leaks include/lib path in devpkg
2019-03-12 2:25 [ptxdist] qt4.make leaks include/lib path in devpkg Jon Ringle
@ 2019-03-13 8:18 ` Michael Olbrich
0 siblings, 0 replies; 2+ messages in thread
From: Michael Olbrich @ 2019-03-13 8:18 UTC (permalink / raw)
To: ptxdist
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
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-03-13 8:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-12 2:25 [ptxdist] qt4.make leaks include/lib path in devpkg Jon Ringle
2019-03-13 8:18 ` Michael Olbrich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox