Merging multimachine.bbclass into the OE.dev core

Merging multimachine.bbclass into the OE.dev core

[Richard Purdie]

Hi,

multimachine has been a kind of second class citizen for a long time
having been maintained in its own class.  We now have things like sdk
generation which implicitly depend on multimachine being used. I can't
think of any reason people wouldn't want to use it and it allows extra
flexibility without imposing any added limitations.

Is it time we merged it into the core classes and made it the default?

The one drawback is it will force an effective wipe tmp for anyone who
wasn't using it before.

Cheers,

Richard

Re: Merging multimachine.bbclass into the OE.dev core

[Koen Kooi]

Richard Purdie wrote:
> Hi,
>
> multimachine has been a kind of second class citizen for a long time
> having been maintained in its own class.  We now have things like sdk
> generation which implicitly depend on multimachine being used. I can't
> think of any reason people wouldn't want to use it and it allows extra
> flexibility without imposing any added limitations.
>
> Is it time we merged it into the core classes and made it the default?

Yes!

regards,

Koen

Re: Merging multimachine.bbclass into the OE.dev core

[Richard Purdie]

On Mon, 2008-06-02 at 11:26 +0100, Richard Purdie wrote:
> multimachine has been a kind of second class citizen for a long time
> having been maintained in its own class.  We now have things like sdk
> generation which implicitly depend on multimachine being used. I can't
> think of any reason people wouldn't want to use it and it allows extra
> flexibility without imposing any added limitations.
> 
> Is it time we merged it into the core classes and made it the default?
> 
> The one drawback is it will force an effective wipe tmp for anyone who
> wasn't using it before.

Its been pointed out that some people only use one target and therefore
don't like the longer paths when they don't need them.

I'd propose adding a singlemachine.bbclass which gives the old behaviour
although people using that would do so at their own risk from the
meta-toolchain and sdk.bbclass perspectives.

Cheers,

Richard

Re: Merging multimachine.bbclass into the OE.dev core

[Michael 'Mickey' Lauer]

On Monday 02 June 2008 13:10:13 Richard Purdie wrote:
> On Mon, 2008-06-02 at 11:26 +0100, Richard Purdie wrote:
> > multimachine has been a kind of second class citizen for a long time
> > having been maintained in its own class.  We now have things like sdk
> > generation which implicitly depend on multimachine being used. I can't
> > think of any reason people wouldn't want to use it and it allows extra
> > flexibility without imposing any added limitations.
> >
> > Is it time we merged it into the core classes and made it the default?
> >
> > The one drawback is it will force an effective wipe tmp for anyone who
> > wasn't using it before.
>
> Its been pointed out that some people only use one target and therefore
> don't like the longer paths when they don't need them.
>
> I'd propose adding a singlemachine.bbclass which gives the old behaviour
> although people using that would do so at their own risk from the
> meta-toolchain and sdk.bbclass perspectives.

Yep, very good.

:M: