From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: atk iptables java/classpath java/jamvm
Date: Wed, 14 Jan 2009 09:11:04 +0100 [thread overview]
Message-ID: <20090114081104.GA11127@zelow.no> (raw)
In-Reply-To: <20090113210244.C2A7E76C8E@busybox.osuosl.org>
On Tue, Jan 13, 2009 at 09:02:44PM +0000, ulf at uclibc.org wrote:
>
> Log:
> Use HOST_GLIB for glib installation instead of /usr/bin
>
> +ATK_MAKE_OPT = GLIB_GENMARSHAL=$(HOST_GLIB)/bin/glib-genmarshal GLIB_MKENUMS=$(HOST_GLIB)/bin/glib-mkenums
Any reason we do this instead of using good old PATH?
Using PATH and having STAGING_DIR/BIN first in it will give the user an option
to choose wether he wants to use the host provided or his own.
Thomas.
prev parent reply other threads:[~2009-01-14 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 21:02 [Buildroot] svn commit: trunk/buildroot/package: atk iptables java/classpath java/jamvm ulf at uclibc.org
2009-01-14 8:11 ` Thomas Lundquist [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=20090114081104.GA11127@zelow.no \
--to=lists@zelow.no \
--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