[OE-core] [PATCH 00/15] devtool and externalsrc improvements

[Bruce Ashfield]

On Thu, Feb 19, 2015 at 12:00 PM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> On Thu, 2015-02-19 at 16:55 +0000, Paul Eggleton wrote:
>> On Thursday 19 February 2015 11:47:01 Bruce Ashfield wrote:
>> > On Thu, Feb 19, 2015 at 11:39 AM, Paul Eggleton
>> > <paul.eggleton at linux.intel.com> wrote:
>> > > I've been attempting to enable usage of devtool with the kernel (which
>> > > effectively means using the externalsrc class with the kernel). This
>> > > doesn't really work yet due to lack of handling the kernel configuration,
>> >
>> > I've always insisted/argued and designed in that externalsrc shouldn't touch
>> > the kernel configuration at all.
>> >
>> > You are building a tree that is completely managed outside of the build
>> > system, and getting the kernel configuration in place is part of that
>> > management.
>> >
>> > So I'm not convinced it is a problem that needs to be solved.
>>
>> So, externalsrc still doesn't touch the configuration, and it is not my plan to
>> make it do so. However, users do need some way of setting up that configuration
>> when checking out those sources for the first time, and if that's to be of any
>> use to someone who just wants to make some minor changes, it should be the
>> exact same configuration you get when you build the recipe as normal. That is
>> what I believe "devtool modify" (at least with -x) should be doing, given that
>> it is one means you can use to set up a development environment if you do not
>> have one already.
>>
>> We can certainly talk about the mechanism and work out the best way to do it,
>> such that it fits in with how linux-yocto works and meets user expectations. My
>> intent with this series was to get us to the point where we can at least
>> experiment and have that discussion.
>
> Having the option of triggering the standard configuration process as
> per a usual linux-yocto build but on an external direction, standalone
> may be the best option?

I did try that before, and the tools to run on random trees (I use it
for building
the linux-yocto kernel source out of tree), but they need the fragments and
meta-data to do that configuration.

and when a externalsrc tree is unpacked and checked out, that data won't
by lying around (that being said, I haven't tried the series to see what
exactly is happening).

I always considered externalsrc to be: "here's my tree, I've set it up and
it is ready to build .. go do it!", so I need to think about the best way to
get that next step done (for any kernel, not just linux yocto).

Bruce

>
> Cheers,
>
> Richard
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"