From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 10/10] package/qt5base: provide "qt.conf" to make "qmake" relocatable
Date: Wed, 5 Jul 2017 16:13:17 +0200 [thread overview]
Message-ID: <20170705161317.205dc3ae@windsurf> (raw)
In-Reply-To: <51297962-b3bc-bd68-8dee-3a1ad8ca92ae@grandegger.com>
Hello,
On Wed, 5 Jul 2017 15:48:22 +0200, Wolfgang Grandegger wrote:
> What about making the relocation stuff configurable as shown in the patch below.
> The advantage is that it could also control the generation of the "qt.conf",
> for example.
We don't want to make it configurable, through a Config.in option.
However, we would like to have a separate make target that prepares the
SDK, creates the tarball, etc.
Basically, a normal "make" would not run all the rpath sanitization
logic, absolute path replacement, etc. There should be a separate "make
sdk" target that does this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-05 14:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 16:22 [Buildroot] [PATCH v6 00/10] Make the SDK relocatable Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 01/10] support/scripts: check-host-rpath now handles $ORIGIN/../lib Wolfgang Grandegger
2017-07-05 11:14 ` Thomas Petazzoni
2017-07-04 16:22 ` [Buildroot] [PATCH v6 02/10] package/patchelf: add patch for rpath sanitization under a root directory Wolfgang Grandegger
2017-07-05 11:16 ` Thomas Petazzoni
2017-07-05 12:35 ` Wolfgang Grandegger
2017-07-05 13:13 ` Thomas Petazzoni
2017-07-05 14:26 ` Arnout Vandecappelle
2017-07-04 16:22 ` [Buildroot] [PATCH v6 03/10] support/scripts: add fix-rpath script to sanitize the rpath Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 04/10] core: sanitize RPATH in staging tree at the end of target finalization Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 05/10] core: sanitize RPATH in target " Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 06/10] core: sanitize RPATH in host tree at the very end of the build Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 07/10] support/scripts: add relocate-sdk.sh script for SDK relocation Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 08/10] core: install relocation script and location at the end of the build Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 09/10] external-toolchain: check if a buildroot SDK has already been relocated Wolfgang Grandegger
2017-07-04 16:22 ` [Buildroot] [PATCH v6 10/10] package/qt5base: provide "qt.conf" to make "qmake" relocatable Wolfgang Grandegger
2017-07-05 8:59 ` Arnout Vandecappelle
2017-07-05 9:30 ` Wolfgang Grandegger
2017-07-05 10:28 ` Wolfgang Grandegger
2017-07-05 13:48 ` Wolfgang Grandegger
2017-07-05 14:13 ` Thomas Petazzoni [this message]
2017-07-05 14:33 ` Wolfgang Grandegger
2017-07-05 14:48 ` Thomas Petazzoni
2017-07-05 15:10 ` Wolfgang Grandegger
2017-07-05 14:49 ` Arnout Vandecappelle
2017-07-05 14:34 ` Arnout Vandecappelle
2017-07-05 9:30 ` Thomas Petazzoni
2017-07-05 9:55 ` Wolfgang Grandegger
2017-07-04 17:55 ` [Buildroot] [PATCH v6 00/10] Make the SDK relocatable Arnout Vandecappelle
2017-07-04 19:54 ` Wolfgang Grandegger
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=20170705161317.205dc3ae@windsurf \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.