From: Darren Hart <dvhart@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Josef Ahmad <josef.ahmad@intel.com>,
Chris Larson <clarson@kergoth.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 1/5] grub-efi-native: New recipe to build GRUB EFI images
Date: Thu, 24 Nov 2011 09:14:32 -0800 [thread overview]
Message-ID: <4ECE7B78.706@linux.intel.com> (raw)
In-Reply-To: <EE779348-2CFB-4ABE-BEEE-96E34470DFFD@dominion.thruhere.net>
-----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-----
next prev parent reply other threads:[~2011-11-24 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 8:04 [RFC PATCH 0/5] EFI live image support Darren Hart
2011-11-24 8:05 ` [RFC PATCH 1/5] grub-efi-native: New recipe to build GRUB EFI images Darren Hart
2011-11-24 8:59 ` Koen Kooi
2011-11-24 11:26 ` Richard Purdie
2011-11-24 16:21 ` Darren Hart
2011-11-24 16:51 ` Koen Kooi
2011-11-24 17:14 ` Darren Hart [this message]
2011-11-25 22:57 ` Darren Hart
2011-11-29 8:03 ` Darren Hart
2011-11-29 8:22 ` Koen Kooi
2011-11-29 8:58 ` Darren Hart
2011-11-29 9:16 ` Koen Kooi
2011-11-29 9:19 ` Darren Hart
2011-11-24 8:05 ` [RFC PATCH 2/5] bootimg: Refactor build_hddimg and build_iso routines Darren Hart
2011-11-24 8:05 ` [RFC PATCH 3/5] bootimg: Pull syslinux specific bits into syslinux.bbclass Darren Hart
2011-11-24 8:05 ` [RFC PATCH 4/5] bootimg: Add grub-efi support Darren Hart
2011-11-24 8:05 ` [RFC PATCH 5/5] bootimg: Allow for EFI-only boot images Darren Hart
2011-11-24 8:14 ` [RFC PATCH 0/5] EFI live image support Darren Hart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECE7B78.706@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=josef.ahmad@intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox