All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Building fw_printenv (u-boot utility) for target?
Date: Wed, 22 Sep 2010 22:35:50 +0200	[thread overview]
Message-ID: <87ocbpa53t.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <i7decv$4q1$1@dough.gmane.org> (Grant Edwards's message of "Wed,  22 Sep 2010 17:29:03 +0000 (UTC)")

>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:

Hi,

 Grant> I want fw_printenv on my target, and it would be convenient if
 Grant> buildroot built it and set up the relvent links.  But, AFAICT, I can't
 Grant> have buildroot build the fw_printenv utility without having it do a
 Grant> complete build of U-Boot.  I don't have any need/desire for buildroot
 Grant> to build the bootloader itself, I only need the fw_printenv linux app
 Grant> for the target.  Is that possible with buildroot?

Currently not, is it a big deal to build u-boot as well?
The reason for this is mainly that fw_printenv isn't available
seperately, so we would need to double quite a lot of the u-boot
handling if we were to move it to a seperate package, and they are most
of the time used together.

 Grant> Or should I just build fw_printenv separately and stick it into the
 Grant> filesystem using the custom package?

That's naturally an option as well.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-09-22 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 17:29 [Buildroot] Building fw_printenv (u-boot utility) for target? Grant Edwards
2010-09-22 20:35 ` Peter Korsgaard [this message]
2010-09-22 20:52   ` Grant Edwards

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=87ocbpa53t.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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.