[linux-yocto] KMETA branch/directory redux (yocto #5090)
Peter A. Bigot
pab at pabigot.com
Sat Aug 30 06:08:23 PDT 2014
On 08/29/2014 03:36 PM, Bruce Ashfield wrote:
> On 14-08-29 04:32 PM, Peter A. Bigot wrote:
>
>> mkdir -p .$(dirname $checkpoint_dir)
>> mv $checkpoint_dir .$checkpoint_dir
>>
>> and even that wouldn't do the right thing in all cases.
>
> I'm restricting what is valid, so I don't have to worry about the
> case of deeply nested directories. I only get the top level directory
> name, and rename it. The subdirs don't matter.
I see that now.
It's a bit confusing that the meta_dir inference algorithm in each of
the tools is slightly different (I count at least two functional
variants among about six implementations), but until it actually causes
a problem that's just me being cranky.
>
>> OK. At this stage I just want "bitbake linux-yocto" to work with
>> branches that look like path hierarchies in workspaces that don't
>> attempt to share build areas among multiple meta configurations. Any
>> other capabilities hidden in yocto-kernel-tools are things I haven't
>> encountered yet.
>
> And it already will. I'll confirm with a test, but the changes I have
> don't care what you name the branch anymore. They just look at the
> disk and see what the top level directory is called, and use it as is.
>
I've done a build with poky master-next and it works for me. This'll
make it much easier to track patches locally. Thank you.
Peter
More information about the linux-yocto
mailing list