From: Tom Rini <trini@konsulko.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: how can i add u-boot-fw-utils to my build without u-boot being part of the build?
Date: Fri, 19 Aug 2016 16:16:37 -0400 [thread overview]
Message-ID: <20160819201637.GO5342@bill-the-cat> (raw)
In-Reply-To: <alpine.LFD.2.20.1608181237130.2886@ca624034.mitel.com>
On Thu, Aug 18, 2016 at 12:41:25PM -0400, Robert P. J. Day wrote:
> not sure if i asked this once, but i'm still trying to figure it
> out.
>
> i want to add the u-boot-fw-utils recipe to my current build, but
> u-boot is *not* part of the relevant BSP layer -- u-boot is being
> configured and built elsewhere, and that's not changing for the
> foreseeable future.
>
> the good news is that those utilities don't need to have any info on
> the default environment for u-boot -- they need only have access to
> the environment in flash, and there is a /etc/fw_env.config file that
> is all set up and ready to go and referring to the correct device and
> offset in flash.
>
> so how do i specify that i want to add that recipe to my build,
> while saying, "don't worry about the default environment, you don't
> need it." can that be done? thanks.
The "easy" way out here is to just set a valid (as in, compiles)
UBOOT_MACHINE and then not worry about installing U-Boot from the OE
build. You can ASSUME_PROVIDED away u-boot itself, but you still need
to have a UBOOT_MACHINE set so that we configure U-Boot before building
the tools (And you must configure before building).
--
Tom
next prev parent reply other threads:[~2016-08-19 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 16:41 how can i add u-boot-fw-utils to my build without u-boot being part of the build? Robert P. J. Day
2016-08-19 20:16 ` Tom Rini [this message]
2016-08-21 13:59 ` Robert P. J. Day
2016-08-21 15:04 ` Tom Rini
2016-08-21 15:51 ` Robert P. J. Day
2016-08-22 8:34 ` Javier Viguera
2016-08-25 10:51 ` Robert P. J. Day
2016-08-25 14:31 ` Robert P. J. Day
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=20160819201637.GO5342@bill-the-cat \
--to=trini@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.