From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Josef Ahmad <josef.ahmad@intel.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Chris Larson <clarson@kergoth.com>
Subject: Re: [RFC PATCH 1/5] grub-efi-native: New recipe to build GRUB EFI images
Date: Tue, 29 Nov 2011 00:58:18 -0800 [thread overview]
Message-ID: <4ED49EAA.7040707@linux.intel.com> (raw)
In-Reply-To: <29FCBED2-0BFC-420A-988F-B11490D51CC1@dominion.thruhere.net>
On 11/29/2011 12:22 AM, Koen Kooi wrote:
>
> Op 29 nov. 2011, om 09:03 heeft Darren Hart het volgende geschreven:
>
>> On 11/25/2011 02:57 PM, Darren Hart wrote:
>>>
>>>
>>> On 11/24/2011 12:05 AM, Darren Hart wrote:
>>>> 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), this recipe builds the utils for the host and
>>>> passes an appropriate --target argument to the GRUB configure script
>>>> to build the modules for the target arch. The only output of this
>>>> recipe is an EFI image in the deploy directory.
>>>
>>> The grub-help list came through with an alternative approach:
>>>
>>> "./configure CC=powerpc-linux-gcc --host=ppc-linux-gnu --target=i386
>>> --with-platform=pc TARGET_CC=i386-linux-gcc"
>>>
>>> This would allow for building on a host of arch ppc for a target of arch
>>> i386.
>>>
>>> Would it be preferable then to build this as a target package and
>>> manipuate the configure flags to use the BUILD_CC ? I presume a similar
>>> PN rename would be desirable to account for the HOST component of the
>>> build as I used here for the TARGET on the -native version?
>>
>> I have been working on trying to get this working as a target recipe. I've
>> resolved a number of issues, but something is still biting me and I haven't been
>> able to sort out what. I would really appreciate a few more sets of eyes on
>> this.
>>
>> I have pushed my dvhart/efi/dev branch to poky-contrib for reference:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/?h=dvhart/efi/dev
>>
>> When building this recipe
>
> This is against poky, so I can't build it. If it was against
> OE-core, like one would expect on the OE-core mailing list,
> I could build it.
OK, fair enough.
git://git.infradead.org/srv/git/users/dvhart/oe-core.git dvhart/efi/dev
I just fixed up the patch series - untested.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-11-29 9:04 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
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 [this message]
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=4ED49EAA.7040707@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.