From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>,
"Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Enabling uninative by default in oe-core?
Date: Fri, 18 Nov 2016 08:03:26 +0000 [thread overview]
Message-ID: <1479456206.28508.104.camel@linuxfoundation.org> (raw)
In-Reply-To: <AA4AB54F-B782-4CFC-9E77-512EAFE73399@dominion.thruhere.net>
On Fri, 2016-11-18 at 08:15 +0100, Koen Kooi wrote:
> >
> > Op 17 nov. 2016, om 18:31 heeft Burton, Ross <ross.burton@intel.com
> > > het volgende geschreven:
> >
> > Hi,
> >
> > Background: uninative is a class that downloads a precompiled host
> > glibc
> Why can’t OE build it on-demand? What’s next, requiring prebuilt
> toolchains?
Its a chicken and egg problem.
We could add a special "uninativesdk" BBCLASSEXTEND range of targets,
then require that it built before we build anything native (or anything
that needs a native tool). This would push build times up 'a little'
and I suspect might not be popular. So the reason we "can't" is that
its impractical, not an absolute technical constraint.
Cheers,
Richard
next prev parent reply other threads:[~2016-11-18 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 17:31 Enabling uninative by default in oe-core? Burton, Ross
2016-11-17 18:06 ` Khem Raj
2016-11-17 18:50 ` [Openembedded-architecture] " Denys Dmytriyenko
2016-11-17 23:22 ` Khem Raj
2016-11-17 18:56 ` Nicolas Dechesne
2016-11-17 23:19 ` Khem Raj
2016-11-17 21:47 ` [Openembedded-architecture] " Mark Hatle
2016-11-18 7:15 ` Koen Kooi
2016-11-18 8:03 ` Richard Purdie [this message]
2016-11-18 16:28 ` akuster808
2016-11-18 18:06 ` [Openembedded-architecture] " Richard Purdie
2016-11-18 20:50 ` Koen Kooi
2016-11-18 21:17 ` Denys Dmytriyenko
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=1479456206.28508.104.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 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.