Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

[Florian Boor]

Hi,

koen commit schrieb:
> task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

I disagree about this as well - if you want a single toolchain please create a
toolchain package. These ones are intended to provide a full SDK.
I see the need for what you intended to do but don't do it in this way.
What we should do is to have a set of SDKs that provide both toolchain and
libraries and packages with only a basic toolchain.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76

Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

[Koen Kooi]

Quoting Florian Boor <florian.boor@kernelconcepts.de>:

> Hi,
>
> koen commit schrieb:
> > task-sdk-sbox, task-sdk: clean out base sdk packages, they should only
> contain a toolchain
>
> I disagree about this as well - if you want a single toolchain please create
> a
> toolchain package. These ones are intended to provide a full SDK.
> I see the need for what you intended to do but don't do it in this way.
> What we should do is to have a set of SDKs that provide both toolchain and
> libraries and packages with only a basic toolchain.

Right, and my changes allow that, you just add tasks *outside* of
task-{sdk,sbox}.bb and you get what you want. With your changes peope have to
*needlessly* *duplicate* task-{sdk,sbox} if they just want a simple toolchain
(without building 3/4 of OE).
So please keep task-{sbox,sdk} clean and generic, otherwise we have multiple
copies of sdk and sed magic no-one understands enough to maintain.
Does my plan sound ok to you?

regards,

Koen

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

[Sergey Lapin]

Koen Kooi wrote:
>
> 
> Right, and my changes allow that, you just add tasks *outside* of
Could you please provide some example here?

Thanks a lot.
S.

Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

[Florian Boor]

Hi,

Koen Kooi schrieb:
> Quoting Florian Boor <florian.boor@kernelconcepts.de>:

> Right, and my changes allow that, you just add tasks *outside* of
> task-{sdk,sbox}.bb and you get what you want. With your changes peope have to
> *needlessly* *duplicate* task-{sdk,sbox} if they just want a simple toolchain
> (without building 3/4 of OE).
> So please keep task-{sbox,sdk} clean and generic, otherwise we have multiple
> copies of sdk and sed magic no-one understands enough to maintain.
> Does my plan sound ok to you?

basically yes - but I would have discussed this before applying these changes.
Our SDK packages always contained more than a basic toolchain and if this should
change we should discuss it before acting and causing needless extra effort.

I'll try to sort things in a way that we get separate SDK packages for each
purpose and without removing things from existing SDK packages blindly. Maybe we
can move all the magic to the SDK class anyway.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76

Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

[Florian Boor]

Hi again,

Florian Boor schrieb:

> I'll try to sort things in a way that we get separate SDK packages for each
> purpose and without removing things from existing SDK packages blindly. Maybe we
> can move all the magic to the SDK class anyway.

I just pushed these changes. Please take a look and test if it does what it is
expected to do. So far it is just a draft that definitely wants some further
improvement. My major focus so far was to get a better base for flexible SDK
targets without loosing the existing functional targets.
This involved some changes:
task-sdk-base was split out from task-sdk.bb into a separate task-sdk-base
package. The former meta-sdk is mostly provided by meta-sdk-gpe now, the Opie
SDK might want a similar one in future. The same happened for the sbox SDK
packages likewise.
meta-sdk is now a quite raw toolchain like Koen intended to get.

I just hope i didn't mix up too much :-)

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76

Re: [oe-commits] org.oe.dev task-sdk-sbox, task-sdk: clean out base sdk packages, they should only contain a toolchain

[Koen Kooi]

Quoting Florian Boor <florian.boor@kernelconcepts.de>:

> Hi,
>
> Koen Kooi schrieb:
> > Quoting Florian Boor <florian.boor@kernelconcepts.de>:
>
> > Right, and my changes allow that, you just add tasks *outside* of
> > task-{sdk,sbox}.bb and you get what you want. With your changes peope have
> to
> > *needlessly* *duplicate* task-{sdk,sbox} if they just want a simple
> toolchain
> > (without building 3/4 of OE).
> > So please keep task-{sbox,sdk} clean and generic, otherwise we have
> multiple
> > copies of sdk and sed magic no-one understands enough to maintain.
> > Does my plan sound ok to you?
>
> basically yes - but I would have discussed this before applying these
> changes.
> Our SDK packages always contained more than a basic toolchain and if this
> should
> change we should discuss it before acting and causing needless extra effort.
>
> I'll try to sort things in a way that we get separate SDK packages for each
> purpose and without removing things from existing SDK packages blindly. Maybe
> we
> can move all the magic to the SDK class anyway.

Thanks for looking at it!

regards,

Koen



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.