[OE-core] [RFC PATCH 1/5] grub-efi-native: New recipe to build GRUB EFI images

Darren Hart dvhart at linux.intel.com
Thu Nov 24 17:14:32 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 11/24/2011 08:51 AM, Koen Kooi wrote:
> 
> Op 24 nov. 2011, om 12:26 heeft Richard Purdie het volgende 
> geschreven:
> 
>> On Thu, 2011-11-24 at 09:59 +0100, Koen Kooi wrote:
>>> Op 24 nov. 2011, om 09:05 heeft Darren Hart het volgende 
>>> geschreven:
>>> 
>>>> Add a recipe to build the GRUB efi images. This recipe is 
>>>> written as a native recipe as the resulting GRUB utils are 
>>>> required to assemble the final image. Rather than build a 
>>>> native and a target recipe (and increase build times),
>>> 
>>> That's a false dilemma. If you write it as a regular recipe
>>> with BBCLASSEXTEND=native your buildtime doesn't increase
>> 
>> That isn't true, if you build a target and a native version your 
>> build time does increase. Using BBCLASSEXTEND does improve
>> parsing time over having two separate recipes though.
> 
> Are you really saying that 'bitbake grub-native' will build both 
> versions if you use BBCLASSEXTEND!?!?! If not, it remains a false 
> dilemma.

No, that isn't it. Because of the way grub builds, you need the utils
in HOST_ARCH and the grub modules in TARGET_ARCH. Grub has a
monolithic build system, so in order to do this with BBCLASSEXTEND, we
would need to have grub-efi depend on grub-efi-native so that the
final do_mkimage task could use the -native version of grub-mkimage to
assemble the target-built modules into a final binary.

This approach builds grub natively and sets the --target to the
TARGET_ARCH so the modules are built for the target. This is why I'm
making the distinction between build the grub tools for deployment and
building the grub efi boot image. The approach to each is different,
and this recipe generates the boot image for the target.


- -- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOznttAAoJEKbMaAwKp364dG0H/0tScwNt0pc9gHDXDELdhCvp
JGJ8soO+yWgksG9o/p077oysd7HMm24Tq//m7FuRzgm0D2JymYwPwdLe06mA1ARs
BpwtvltUW5SLaWzJVeamxeNn5cDpdIcyaa904BdS2Ink/alZgTdoV60qh9LvElIh
P70Pb/GeV/Po5OLALmnYuEV39JPnRxz7RfaXr7qU/0e0JVGKxXa/hrBp8ZgzpYI4
WvGns2LrZRPi/Fp93Vc312NfZYa2y/s9H8ji+B2Nvdza99Zo9y4xtWSf9bDRn+4J
04Kw/CFUe4GqXrIoBATLvm8LmcS/fLaqtVY5Ewz5bSnPFRvXyYApmmNvWpy5hGs=
=LaXk
-----END PGP SIGNATURE-----




More information about the Openembedded-core mailing list