Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hamish at uclibc.org <hamish@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/freetype
Date: Thu,  4 Sep 2008 18:03:49 -0700 (PDT)	[thread overview]
Message-ID: <20080905010349.6D501F800B@busybox.net> (raw)

Author: hamish
Date: 2008-09-04 18:03:45 -0700 (Thu, 04 Sep 2008)
New Revision: 23325

Log:
Version bump to 2.3.7
This package should be converted to use Makefile.autotools.in by someone who uses it..


Modified:
   trunk/buildroot/package/freetype/Config.in
   trunk/buildroot/package/freetype/freetype.mk


Changeset:
Modified: trunk/buildroot/package/freetype/Config.in
===================================================================
--- trunk/buildroot/package/freetype/Config.in	2008-09-04 16:16:47 UTC (rev 23324)
+++ trunk/buildroot/package/freetype/Config.in	2008-09-05 01:03:45 UTC (rev 23325)
@@ -16,12 +16,12 @@
 	config BR2_FREETYPE_VERSION_2_2_1
 		bool "Freetype 2.2.1"
 
-	config BR2_FREETYPE_VERSION_2_3_5
-		bool "Freetype 2.3.5"
+	config BR2_FREETYPE_VERSION_2_3_7
+		bool "Freetype 2.3.7"
 
 endchoice
 
 config BR2_FREETYPE_VERSION
 	string
 	default "2.2.1"		if BR2_FREETYPE_VERSION_2_2_1
-	default "2.3.5"		if BR2_FREETYPE_VERSION_2_3_5
+	default "2.3.7"		if BR2_FREETYPE_VERSION_2_3_7

Modified: trunk/buildroot/package/freetype/freetype.mk
===================================================================
--- trunk/buildroot/package/freetype/freetype.mk	2008-09-04 16:16:47 UTC (rev 23324)
+++ trunk/buildroot/package/freetype/freetype.mk	2008-09-05 01:03:45 UTC (rev 23325)
@@ -16,7 +16,7 @@
 
 $(FREETYPE_DIR)/.unpacked: $(DL_DIR)/$(FREETYPE_SOURCE)
 	$(FREETYPE_CAT) $(DL_DIR)/$(FREETYPE_SOURCE) | tar -C $(BUILD_DIR) $(TAR_OPTIONS) -
-	toolchain/patch-kernel.sh $(FREETYPE_DIR) package/freetype/ \*.patch
+	toolchain/patch-kernel.sh $(FREETYPE_DIR) package/freetype/ freetype-$(FREETYPE_VERSION)-\*.patch
 	$(CONFIG_UPDATE) $(FREETYPE_DIR)
 	$(CONFIG_UPDATE) $(FREETYPE_DIR)/builds/unix
 	touch $@

             reply	other threads:[~2008-09-05  1:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  1:03 hamish at uclibc.org [this message]
2008-09-05  9:52 ` [Buildroot] svn commit: trunk/buildroot/package/freetype Peter Korsgaard
2008-09-05 12:53   ` Hamish Moffatt
2008-09-05 18:31     ` Peter Korsgaard
2008-09-06  4:22       ` Hamish Moffatt
2008-09-05 17:44   ` danieljlaird at hotmail.com
  -- strict thread matches above, loose matches on Subject: below --
2009-01-24 10:20 jacmet at uclibc.org
2009-01-24  8:31 jacmet at uclibc.org
2009-01-16  9:02 laird at uclibc.org
2009-01-08  8:27 jacmet at uclibc.org
2008-12-08 13:42 jacmet at uclibc.org
2008-12-08  4:43 hamish at uclibc.org
2008-11-11 11:33 laird at uclibc.org
2009-01-24  8:28 ` Peter Korsgaard
2008-11-10 21:43 hartleys
2008-10-09 12:50 laird at uclibc.org
2008-07-17 13:20 jacmet at uclibc.org
2008-07-04  2:57 correa at uclibc.org
2008-07-05 19:08 ` Peter Korsgaard
2008-05-22 21:30 ulf at uclibc.org
2008-04-25 16:45 ninevoltz at uclibc.org
2008-03-06 18:10 ninevoltz at uclibc.org
2007-11-16 10:16 vanokuten at uclibc.org
2007-09-23  9:55 ulf at uclibc.org
2007-08-14  6:28 ulf at uclibc.org
2007-01-16 19:51 aldot at uclibc.org
2007-01-10 23:54 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=20080905010349.6D501F800B@busybox.net \
    --to=hamish@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