From: andersen at uclibc.org <andersen@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libgtk2
Date: Sun, 14 Jan 2007 15:27:26 -0800 (PST) [thread overview]
Message-ID: <20070114232726.D964D48614@busybox.net> (raw)
Author: andersen
Date: 2007-01-14 15:27:26 -0800 (Sun, 14 Jan 2007)
New Revision: 17310
Log:
oops, embed $(STAGING_DIR) rather than hard coding my home dir...
Modified:
trunk/buildroot/package/libgtk2/libgtk2.mk
Changeset:
Modified: trunk/buildroot/package/libgtk2/libgtk2.mk
===================================================================
--- trunk/buildroot/package/libgtk2/libgtk2.mk 2007-01-14 23:26:15 UTC (rev 17309)
+++ trunk/buildroot/package/libgtk2/libgtk2.mk 2007-01-14 23:27:26 UTC (rev 17310)
@@ -88,7 +88,7 @@
# I dont yet understand why configure is not doing this right
# TODO: also remove 'odd-include-problem.patch' when this is fixed
$(SED) "s,^GDK_DEP_CFLAGS=.*,GDK_DEP_CFLAGS=\'-pthread -I$(STAGING_DIR)/include/glib-2.0 -I$(STAGING_DIR)/lib/glib-2.0/include -I$(STAGING_DIR)/include/pango-1.0 -I$(STAGING_DIR)/include/cairo\',g" $(LIBGTK2_DIR)/configure
- $(SED) "s,^GDK_DEP_LIBS=.*,GDK_DEP_LIBS=\'-L/home/andersen/SVN/buildroot/build_i686/staging_dir/lib -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lfontconfig -lXext -lXrender -lX11 -lXinerama -lXrandr -lXcursor -lXfixes -lXft -lm\',g" $(LIBGTK2_DIR)/configure
+ $(SED) "s,^GDK_DEP_LIBS=.*,GDK_DEP_LIBS=\'-L$(STAGING_DIR)/lib -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lfontconfig -lXext -lXrender -lX11 -lXinerama -lXrandr -lXcursor -lXfixes -lXft -lm\',g" $(LIBGTK2_DIR)/configure
(cd $(LIBGTK2_DIR); rm -rf config.cache; \
$(LIBGTK2_BUILD_ENV) \
./configure \
next reply other threads:[~2007-01-14 23:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 23:27 andersen at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-18 10:57 [Buildroot] svn commit: trunk/buildroot/package/libgtk2 ulf at uclibc.org
2009-01-18 11:05 ` Peter Korsgaard
2009-01-18 13:11 ` Sven Neumann
2009-01-18 13:43 ` Daniel Laird
2009-01-18 13:48 ` Peter Korsgaard
2009-01-14 22:11 ulf at uclibc.org
2009-01-15 8:36 ` Thomas Lundquist
2009-01-15 20:18 ` Ulf Samuelsson
2009-01-15 20:26 ` Peter Korsgaard
2009-01-15 20:37 ` Ulf Samuelsson
2008-12-31 9:35 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-10-27 9:45 jacmet at uclibc.org
2008-10-18 7:00 jacmet at uclibc.org
2008-08-26 13:45 laird at uclibc.org
2008-08-26 12:19 laird at uclibc.org
2008-08-26 13:15 ` Peter Korsgaard
2008-08-26 13:32 ` Daniel Laird
2008-08-26 13:38 ` Peter Korsgaard
2008-08-26 14:04 ` Bernhard Reutner-Fischer
2008-08-26 14:07 ` Bernhard Reutner-Fischer
2008-08-26 14:54 ` Peter Korsgaard
2008-08-26 13:48 ` Bernhard Reutner-Fischer
2008-08-26 14:07 ` Peter Korsgaard
2008-08-26 14:11 ` Bernhard Reutner-Fischer
2008-08-26 14:13 ` Daniel Laird
2008-08-26 13:42 ` Ormund Williams
2008-08-26 13:49 ` Daniel Laird
2008-07-08 10:09 ulf at uclibc.org
2008-07-07 11:09 ulf at uclibc.org
2008-07-06 6:25 ulf at uclibc.org
2007-02-01 19:20 andersen at uclibc.org
2007-01-17 11:27 jacmet at uclibc.org
2007-01-17 0:04 andersen at uclibc.org
2007-01-14 23:26 andersen at uclibc.org
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=20070114232726.D964D48614@busybox.net \
--to=andersen@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