From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] qt4.make leaks include/lib path in devpkg
Date: Wed, 13 Mar 2019 09:18:15 +0100 [thread overview]
Message-ID: <20190313081815.k67e7bkaycslqsmt@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjwocQccELdHjg0htK_hhEUqZP=_XNPogD4ze4vK_t4uTQ@mail.gmail.com>
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
prev parent reply other threads:[~2019-03-13 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 2:25 Jon Ringle
2019-03-13 8:18 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190313081815.k67e7bkaycslqsmt@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox