From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9] qt5: install missing examples
Date: Sun, 17 Jun 2018 14:44:42 +0200 [thread overview]
Message-ID: <20180617144442.3fc03f6e@windsurf> (raw)
In-Reply-To: <20180612123206.31523-1-gael.portay@savoirfairelinux.com>
Hello Ga?l,
On Tue, 12 Jun 2018 08:31:57 -0400, Ga?l PORTAY wrote:
> Regards,
> Ga?l PORTAY (9):
> qt5canvas3d: install examples to target
> qt5location: install examples to target
> qt5quickcontrols: install examples to target
> qt5script: install examples to target
> qt5wayland: install examples to target
> qt5svg: install examples to target
> qt5serialbus: install examples to target
> qt5serialport: install examples to target
> qt5sensors: install examples to target
Thanks, I've applied all your patches.
However, I am not super happy with how we install Qt5 packages right
now. What we do is:
- Staging installation: "make install", with no DESTDIR or anything
similar
- Target installation: manual copy.
Ideally, I'd prefer if we could do:
- Staging installation: make DESTDIR=$(STAGING_DIR) install
- Target installation: make DESTDIR=$(TARGET_DIR) install
Unfortunately, this doesn't work as-is, because the $(STAGING_DIR)
location is hardcoded at Qt configure time, so it doesn't work
immediately to do separate installation for staging and target. I know
Arnout briefly looked into this during the last Buildroot hackathon.
However, it would be nice if someone could have a deeper look into
this. It would greatly help to simplify our Qt5 packages.
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 12:44 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 ` Thomas Petazzoni [this message]
2018-06-17 20:05 ` [Buildroot] [PATCH 0/9] qt5: install missing examples Gaël PORTAY
2018-06-17 20:48 ` Thomas Petazzoni
2018-06-17 21:11 ` Gaël PORTAY
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=20180617144442.3fc03f6e@windsurf \
--to=thomas.petazzoni@bootlin.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