Re: [PATCH] kernel.bbclass: add deploy link to KERNEL_IMAGETYPE

[Darren Hart <dvhart@linux.intel.com>]

On 05/17/2012 07:58 AM, Koen Kooi wrote:
> 
> Op 17 mei 2012, om 16:46 heeft Darren Hart het volgende geschreven:
> 
>> On 05/15/2012 06:25 PM, Christopher Larson wrote:
>>> From: Christopher Larson <chris_larson@mentor.com>
>>> 
>>> It's common to provide a non-machine-suffixed link in
>>> DEPLOY_DIR_IMAGE, so let's be consistent and do so here as well.
>> 
>> This of course means that building two machines in the same build
>> dir will result in overwriting the latest non-machine-suffixed
>> link (provided they are the same image type)
> 
> Actually it doesn't. At least not on angstrom, shr and slugos:
> 
> koen@dominion:/OE/tentacle/sources/meta-angstrom$ git grep
> DEPLOY_DIR_IMAGE conf/distro/include/angstrom.inc:DEPLOY_DIR_IMAGE =
> "${DEPLOY_DIR}/images/${MACHINE}"

That seems like a good idea to me. It would make more sense to me for
that to be the default. Having a DISTRO define BUILD policy seems a bit
backwards.

Would anyone object to including ${MACHINE} in the deploy dir by default?

> 
> The above was mentioned a few weeks ago, but it looks like no one but
> the distros above and Chris care about proper multimachine builds. 

Awe, you were doing so well up until there.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel