All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] use of HOST_GLIB
Date: Wed, 23 Sep 2009 21:14:06 +0200	[thread overview]
Message-ID: <1253733246.14595.19.camel@bender> (raw)
In-Reply-To: <87pr9hv6i2.fsf@macbook.be.48ers.dk>

Hi,

On Wed, 2009-09-23 at 20:52 +0200, Peter Korsgaard wrote:

>  >> 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?

Well, it's pretty much the same story as with glib-genmarshal, perhaps
not as commonly used though. glib-mkenums is a code-generation tool that
glib installs and that applications and libraries using glib may use in
their Makefiles. The AM_PATH_GLIB_2_0() macro uses pkg-config to find
out where glib has installed it and defines the GLIB_MKENUMS variable
pointing to the binary. There is also gobject-query, which is probably
even less commonly used.

So yes, I think there should be a HOST_GLIB_MKENUMS variable and I think
that LIBGLIB2_HOST_BINARY should be rather be named
HOST_GLIB_GENMARSHAL.


Sven

      reply	other threads:[~2009-09-23 19:14 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
2009-09-23 19:14       ` Sven Neumann [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=1253733246.14595.19.camel@bender \
    --to=s.neumann@raumfeld.com \
    --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.