Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] build process needs host executable
Date: Mon, 27 Apr 2009 08:59:29 +0200	[thread overview]
Message-ID: <87preyh99q.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090416212454.5D43A1C806D@whitealder.osuosl.org> (Chris Bare's message of "Thu\, 16 Apr 2009 17\:23\:16 -0400 \(EDT\)")

>>>>> "Chris" == Chris Bare <chris@bareflix.com> writes:

Hi,

 Chris> Can anyone point me to an example of how this was dealt with
 Chris> in other packages?  In this case, I don't think the executable
 Chris> is needed on the target, it is just part of the build process.

Look at the packages we have which first build a -host version and
uses the binaries from there. dbus-glib is an example (it needs
dbus-binding-tool).

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-04-27  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 21:23 [Buildroot] build process needs host executable Chris Bare
2009-04-27  6:59 ` Peter Korsgaard [this message]

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=87preyh99q.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox