Actually, I'm going to revert this commit out of master. The
autobuilder doesn't start up when it is applied.
I don't have time to look at why right now, but I'll take a look when
I get back.
-b
On Tue, Jul 2, 2013 at 3:59 PM, Flanagan, Elizabeth
wrote:
> I'm going to pull these for now, but I'
I'm going to pull these for now, but I'll probably end up doing this
significantly different when we settle on whatever solution (be it
LAYERVERSION or whatever) to identify build process breakage.
-b
On Tue, Jul 2, 2013 at 8:28 AM, Flanagan, Elizabeth
wrote:
> On Fri, Jun 28, 2013 at 9:01 AM,
On Fri, Jun 28, 2013 at 9:01 AM, Trevor Woerner
wrote:
> Just out of curiosity...
>
> On 27 June 2013 06:06, Ross Burton wrote:
>> buildset-config/nightly-arm.conf |2 ++
>> buildset-config/nightly-fsl-arm.conf |2 ++
>> buildset-config/nightly-fsl-ppc.conf |2 ++
>> buildset-con
On Jul 1, 2013, at 2:16 AM, Ross Burton wrote:
> On Fri, 2013-06-28 at 15:44 -0600, Gary Thomas wrote:
>> On 2013-06-27 04:06, Ross Burton wrote:
>>> The meta-toolchain* recipes are deprecated, so when building
>>> meta-toolchain-gmae
>>> also build the SDK for core-image-sato.
>>>
>>> Signed-
On 1 July 2013 10:24, Kumita Bruce wrote:
> What's the reason to deprecate meta-toolchain that is for standalone
> cross-compiler generation? Is there a replacement?
For full SDKs, generation from images is trivial now and means you
don't need to replicate everything. I've no idea about the prod
What's the reason to deprecate meta-toolchain that is for standalone
cross-compiler generation? Is there a replacement?
Cheers,
Bruce
On Mon, Jul 1, 2013 at 5:16 PM, Ross Burton wrote:
> On Fri, 2013-06-28 at 15:44 -0600, Gary Thomas wrote:
> > On 2013-06-27 04:06, Ross Burton wrote:
> > >
On Fri, 2013-06-28 at 15:44 -0600, Gary Thomas wrote:
> On 2013-06-27 04:06, Ross Burton wrote:
> > The meta-toolchain* recipes are deprecated, so when building
> > meta-toolchain-gmae
> > also build the SDK for core-image-sato.
> >
> > Signed-off-by: Ross Burton
>
> If/when the meta-toolchain r
On Fri, 2013-06-28 at 14:24 -0700, Khem Raj wrote:
> as an aside, if meta-toolchain is deprecated why should we carry
> meta-toolchain-gmae as well? it seems a special SDK
> only target. I think it will be better to have sdks from images all
> the time.
Because the QA testing for Danny and likely
On 2013-06-27 04:06, Ross Burton wrote:
The meta-toolchain* recipes are deprecated, so when building meta-toolchain-gmae
also build the SDK for core-image-sato.
Signed-off-by: Ross Burton
If/when the meta-toolchain recipes go away, how do I create a stand-alone
toolchain
derived from Poky/Yo
On Friday 28 June 2013 12:01:39 Trevor Woerner wrote:
> Just out of curiosity...
>
> On 27 June 2013 06:06, Ross Burton wrote:
> > buildset-config/nightly-arm.conf |2 ++
> > buildset-config/nightly-fsl-arm.conf |2 ++
> > buildset-config/nightly-fsl-ppc.conf |2 ++
> > buildset-
On Jun 27, 2013, at 3:06 AM, Ross Burton wrote:
> The meta-toolchain* recipes are deprecated, so when building
> meta-toolchain-gmae
> also build the SDK for core-image-sato.
as an aside, if meta-toolchain is deprecated why should we carry
meta-toolchain-gmae as well? it seems a special SDK
o
Just out of curiosity...
On 27 June 2013 06:06, Ross Burton wrote:
> buildset-config/nightly-arm.conf |2 ++
> buildset-config/nightly-fsl-arm.conf |2 ++
> buildset-config/nightly-fsl-ppc.conf |2 ++
> buildset-config/nightly-mips.conf|2 ++
> buildset-config/nightly-oec
The meta-toolchain* recipes are deprecated, so when building meta-toolchain-gmae
also build the SDK for core-image-sato.
Signed-off-by: Ross Burton
---
buildset-config/nightly-arm.conf |2 ++
buildset-config/nightly-fsl-arm.conf |2 ++
buildset-config/nightly-fsl-ppc.conf |2 ++
13 matches
Mail list logo
