From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 5 Jul 2017 16:48:05 +0200 Subject: [Buildroot] [PATCH v6 10/10] package/qt5base: provide "qt.conf" to make "qmake" relocatable In-Reply-To: References: <1499185359-8293-1-git-send-email-wg@grandegger.com> <1499185359-8293-11-git-send-email-wg@grandegger.com> <57657dbc-eca2-a352-ae7c-902a01c9ce73@grandegger.com> <51297962-b3bc-bd68-8dee-3a1ad8ca92ae@grandegger.com> <20170705161317.205dc3ae@windsurf> Message-ID: <20170705164805.226e3a48@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Wed, 5 Jul 2017 16:33:35 +0200, Wolfgang Grandegger wrote: > > 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. > > Yes I understand, but how do you want to handle static things like the > creation of "qt.conf" required for the relocatable SDK? In order to make sure that the SDK situation is as close to a normal Buildroot usage, I think the qt.conf file should always be created and used by qmake. So basically, the Qt package in Buildroot should create and install this file. Am I missing something here? Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com