From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: Split out bjam build tool and add real native support
Date: Tue, 12 Mar 2013 12:58:51 +0100 [thread overview]
Message-ID: <513F187B.3050207@herbrechtsmeier.net> (raw)
In-Reply-To: <8517DA88-71D7-462E-B068-163831AB5D3C@dominion.thruhere.net>
Am 12.03.2013 11:48, schrieb Koen Kooi:
> Op 12 mrt. 2013, om 11:19 heeft Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net> het volgende geschreven:
>
>> Am 12.03.2013 00:44, schrieb Saul Wold:
>>> On 03/07/2013 08:37 AM, Stefan Herbrechtsmeier wrote:
>>>> The current boost recipe only creates the bjam build tool during
>>>> a native run and thereby is not usable for other native programs
>>>> that depend on a boost library. Split out the build tool into its
>>>> own bjam recipe and add real native support to the boost recipe.
>>>> This allows recipes to depend on native boost libraries without
>>>> increase of the build time for other use cases.
>>>>
>>>> Native compilation of bzip2 isn't working and therefore disabled.
>>>>
>>>> Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
>>>> ---
>>>> meta/recipes-support/boost/bjam_1.53.0.bb | 21 +++++++++++
>>>> meta/recipes-support/boost/boost-1.53.0.inc | 21 +++++++++++
>>>> meta/recipes-support/boost/boost.inc | 49 ++-------------------------
>>>> meta/recipes-support/boost/boost_1.53.0.bb | 6 +--
>>>> 4 files changed, 47 insertions(+), 50 deletions(-)
>>>> create mode 100644 meta/recipes-support/boost/bjam_1.53.0.bb
>>>> create mode 100644 meta/recipes-support/boost/boost-1.53.0.inc
>>>>
>>> This change seems to have caused a failure on my test build:
>> Sorry, I missed the no native case. I rename bjam to bjam-native and send a new patch. Bjam make no sense on the target as it is only used for compiling.
> And what if you need bjam to compile something on the target?
Then you need to add cross compile support to bjam which is outside of
the scope of this patch.
next prev parent reply other threads:[~2013-03-12 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 16:37 [PATCH] boost: Split out bjam build tool and add real native support Stefan Herbrechtsmeier
2013-03-11 23:44 ` Saul Wold
2013-03-12 10:19 ` Stefan Herbrechtsmeier
2013-03-12 10:48 ` Koen Kooi
2013-03-12 11:58 ` Stefan Herbrechtsmeier [this message]
2013-03-12 14:55 ` Stefan Herbrechtsmeier
2013-03-12 14:49 ` [PATCH] boost: Add " Stefan Herbrechtsmeier
2013-03-26 5:55 ` Khem Raj
2013-03-26 7:44 ` Stefan Herbrechtsmeier
2013-03-26 13:02 ` [PATCH V2] " Stefan Herbrechtsmeier
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=513F187B.3050207@herbrechtsmeier.net \
--to=stefan@herbrechtsmeier.net \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/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