From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] use of HOST_GLIB
Date: Wed, 23 Sep 2009 20:52:05 +0200 [thread overview]
Message-ID: <87pr9hv6i2.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1253714491.1618.68.camel@sven> (Sven Neumann's message of "Wed\, 23 Sep 2009 16\:01\:31 +0200")
>>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
Hi,
>> Ahh, those must have been missed when we fixed the glib-genmarshal
>> stuff. The proper variable to use is LIBGLIB2_HOST_BINARY.
Sven> That is a rather strange name. Nothing in LIBGLIB2_HOST_BINARY
Sven> tells me that this is glib-genmarshal. What's the variable to use
Sven> for glib-mkenums then ?
Well, it's just following the approach of the other host packages, but
you can use $(HOST_DIR)/usr/bin/glib-genmarshal as well now that we're
compiling it ourselves. I don't see any references in the tree to a
explicitly defined glib-mkenums, should there be?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-09-23 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 11:54 [Buildroot] use of HOST_GLIB Sven Neumann
2009-09-23 12:54 ` Peter Korsgaard
2009-09-23 14:01 ` Sven Neumann
2009-09-23 18:52 ` Peter Korsgaard [this message]
2009-09-23 19:14 ` Sven Neumann
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=87pr9hv6i2.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