> Op 22 okt. 2014, om 01:28 heeft Marek Vasut <ma...@denx.de> het volgende
> geschreven:
>
> On Monday, October 20, 2014 at 12:26:04 PM, Koen Kooi wrote:
>>> Op 19 okt. 2014, om 21:15 heeft Marek Vasut <ma...@denx.de> het volgende
>>> geschreven:
>>>
>>> Pull the uImage image format generation from kernel.bbclass into
>>> a separate kernel-uimage.bbclass. The recipes which now need to
>>> generate an uImage will have to inherit kernel-uimage instead of
>>> kernel class.
>>
>> To keep backward compatibility, could you rework this into something like:
>>
>> kernel.bbclass:
>> inherit kernel-${KERNEL_IMAGETYPE}
>>
>> kernel-${KERNEL_IMAGETYPE}:
>> inherit kernel-base
>> imagetype stuff
>>
>> kernel-base:
>> old kernel.bbclass stuff
>>
>> That would keep existing BSPs working *and* split out the image types.
>
> Yes, this makes sense. Are there any traps inside kernel.bbclass I should
> be careful about? Like for example ${PN} or other possible variables which
> are set based on the name of the file?
You should be safe, PN is supposed to be completely ignored since the output
packages will all be 'kernel-<foo>' instead of 'linux-myfirstbsp-<foo>'
regards,
Koen
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
