From: "Gaël PORTAY" <gael.portay@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9] qt5: install missing examples
Date: Sun, 17 Jun 2018 17:11:36 -0400 [thread overview]
Message-ID: <20180617211136.soa74rty7nxqjs7h@archlinux> (raw)
In-Reply-To: <20180617224837.33949a3a@windsurf>
Thomas,
On Sun, Jun 17, 2018 at 10:48:37PM +0200, Thomas Petazzoni wrote:
> > (...)
> >
> > There is INSTALL_ROOT variable which looks to be equivalent to DESTDIR.
>
> Yes, but no. The problem is that with the way things are currently
> setup, if you set INSTALL_ROOT to /foo/bar and STAGING_DIR
> is /home/thomas/buildroot/output/staging, then Qt5 stuff will be
> installed in:
>
> /foo/bar/home/thomas/buildroot/output/staging
>
> Which is obviously wrong. And I believe the fact that it does this is
> due to:
>
> -sysroot $(STAGING_DIR) \
>
> when configuring Qt5. Some research is needed to see if a better
> solution is possible :-)
>
I will have a look to that. I have started a fresh build with few
modifications on pathes.
I think it is because of the prefix in qt.conf.in which is sed to
$(HOST_DIR).
[Paths]
Prefix=@@HOST_DIR@@
...
Libraries=/usr/lib
...
Binaries=/usr/bin
...
I will see.
> > Also, I was thinking about a qmake-package or a qt5module-package.
>
> A qmake-package infrastructure might make sense. But beware of Qt4/Qt5
> compatibility. But to me, fixing the first problem is much more
> important/useful.
>
For sure... My first run is to rewrite all <qt5modules>_INSTALL_TARGET
(if possible) using:
$(MAKE) -C ... install INSTALL_ROOT=$(TARGET_DIR)
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com
next prev parent reply other threads:[~2018-06-17 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 12:31 [Buildroot] [PATCH 0/9] qt5: install missing examples Gaël PORTAY
2018-06-12 12:31 ` [Buildroot] [PATCH 1/9] qt5canvas3d: install examples to target Gaël PORTAY
2018-06-12 12:31 ` [Buildroot] [PATCH 2/9] qt5location: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 3/9] qt5quickcontrols: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 4/9] qt5script: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 5/9] qt5wayland: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 6/9] qt5svg: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 7/9] qt5serialbus: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 8/9] qt5serialport: " Gaël PORTAY
2018-06-12 12:32 ` [Buildroot] [PATCH 9/9] qt5sensors: " Gaël PORTAY
2018-06-17 12:44 ` [Buildroot] [PATCH 0/9] qt5: install missing examples Thomas Petazzoni
2018-06-17 20:05 ` Gaël PORTAY
2018-06-17 20:48 ` Thomas Petazzoni
2018-06-17 21:11 ` Gaël PORTAY [this message]
2018-06-19 7:29 ` Arnout Vandecappelle
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=20180617211136.soa74rty7nxqjs7h@archlinux \
--to=gael.portay@savoirfairelinux.com \
--cc=buildroot@busybox.net \
/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