From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt5base: remove nostrip qmake.conf config option
Date: Fri, 27 Oct 2017 19:49:17 +0200 [thread overview]
Message-ID: <20171027194917.3f3dd39e@windsurf> (raw)
In-Reply-To: <20171027193047.388c0893@gmx.net>
Hello,
On Fri, 27 Oct 2017 19:30:47 +0200, Peter Seiderer wrote:
> > I think we do want qmake to *not* strip anything, and leave it to
> > Buildroot's BR2_STRIP_strip option to decide whether stripping should
> > happen or not.
>
> Mhhh, I see the reason for the in-buildroot usage of qmake, but still a bit
> annoying for out-of-buildroot usage (but maybe a 'qmake CONIFG-=nostrip'
> works here),
Hum, OK, I see the problem.
> would still prefer to keep the simple/original qmake default and
> (maybe) add an additional 'CONFIG+=nostrip' to all in-buildroot qmake
> usages?
Having to explicitly specify CONFIG+=nostrip to each and every qmake
based package is not going to be very nice. Can we have a Buildroot
specific qmake.conf that inherits a common one, and is used by
Buildroot when building qmake packages ?
Or is it enough to just specify CONFIG+=nostrip in $(QT_QMAKE) and
$(QT5_QMAKE) ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-27 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 16:05 [Buildroot] [PATCH v1] qt5base: remove nostrip qmake.conf config option Peter Seiderer
2017-10-27 16:34 ` Thomas Petazzoni
2017-10-27 17:30 ` Peter Seiderer
2017-10-27 17:49 ` Thomas Petazzoni [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=20171027194917.3f3dd39e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox