From: Mike Crowe <mac@mcrowe.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: boost: Ineffective compileflags and linkflags in user-config.jam
Date: Tue, 18 Feb 2014 21:24:42 +0000 [thread overview]
Message-ID: <20140218212442.GA22168@mcrowe.com> (raw)
In-Reply-To: <CAMKF1sr1Aa86Bpbkas6rBh_XPQtLLeraHO17jMDtggsZUh7-7w@mail.gmail.com>
On Tuesday 18 February 2014 at 13:01:31 -0800, Khem Raj wrote:
> On Tue, Feb 18, 2014 at 12:53 PM, Mike Crowe <mac@mcrowe.com> wrote:
> > or should users of this recipe be given a convenient ability to override
> > the compileflags, with perhaps something like:
> >
> > 'using gcc ; 4.3.1 : ${CXX} : <cflags>"${CFLAGS}" <cxxflags>"${CXXFLAGS}" ;'
>
> this one. care to send a patch ?
Hi Khem,
I can do once I've tested it against current master.
Thanks.
Mike.
next prev parent reply other threads:[~2014-02-18 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 20:53 boost: Ineffective compileflags and linkflags in user-config.jam Mike Crowe
2014-02-18 21:01 ` Khem Raj
2014-02-18 21:24 ` Mike Crowe [this message]
2014-02-19 10:40 ` [PATCH] boost: Pass CFLAGS, CXXFLAGS and LDFLAGS correctly into boost.build Mike Crowe
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=20140218212442.GA22168@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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