All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/boost: fixup Optimization flag in boost build
Date: Fri, 28 Aug 2020 17:03:17 +0200	[thread overview]
Message-ID: <875z92yfre.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200807085811.672959-1-buildroot@heine.tech> (Michael Nosthoff's message of "Fri, 7 Aug 2020 10:58:12 +0200")

>>>>> "Michael" == Michael Nosthoff <buildroot@heine.tech> writes:

 > When building with Boost Build the CXXFLAGS are extended depending
 > on the optimization level set. When not defined explicitly the
 > optimization level depends on the <variant>. For release it's 'speed'
 > and for debug it's set to 'off'

 > These flags overwrite the -O flag passed in with TARGET_CXXFLAGS as
 > it is appended when calling g++.

 > This commit sets the Optimization flags generated by Boost Build
 > to the value of TARGET_OPTIMIZATION no matter what level is used.

 > As Boost Build offers no nice way to alter those values the gcc
 > toolchain file is altered directly.

 > Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
 > ---

 > v1 -> v2:
 >   - use sed to manipulate gcc.jam directly
 >   - remove extending user-config.jam

Committed to 2020.02.x and 2020.05.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2020-08-28 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 12:41 [Buildroot] [PATCH] package/boost: fixup Optimization flag in boost build Michael Nosthoff
2020-08-06 20:16 ` Yann E. MORIN
2020-08-07  8:32   ` Michael Nosthoff
2020-08-07  8:58 ` [Buildroot] [PATCH v2] " Michael Nosthoff
2020-08-07 19:19   ` Yann E. MORIN
2020-08-28 15:03   ` Peter Korsgaard [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=875z92yfre.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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.