gitolite/buildrootschalter
gitolite/buildrootschalter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
e7b38c71ce
buildrootschalter/package/fontconfig/fontconfig.mk

69 lines
2.3 KiB
Makefile
Raw Normal View History

add fontconfig package
2007-01-14 04:39:53 +01:00
#############################################################
#
# fontconfig
#
#############################################################
fontconfig: bump version
2008-06-26 16:04:39 +02:00
FONTCONFIG_VERSION = 2.6.0
updated fontconfig
2008-03-06 19:09:37 +01:00
FONTCONFIG_SOURCE = fontconfig-$(FONTCONFIG_VERSION).tar.gz
FONTCONFIG_SITE = http://fontconfig.org/release
Add a parallel compilation fix for fontconfig This patch adds a patch to fix bug https://bugs.freedesktop.org/show_bug.cgi?id=16464 affecting parallel compilation of fontconfig. The patch is the one proposed in the bugzilla entry, available at https://bugs.freedesktop.org/attachment.cgi?id=17294. Without this patch, the compilation (at BR2_JLEVEL > 1) of fontconfig sometimes fails with: In file included from fc-case.c:25: ../src/fcint.h:118:21: error: fcalias.h: No such file or directory Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-11 20:38:10 +01:00
FONTCONFIG_AUTORECONF = YES
Adding Central config.cache options The following changes allow for use of a central configure cache file. This speeds up configuration of packages. Its use is configurable at the top level (BR2_CONFIG_CACHE - default n). Old style makefiles can use it if they use the following MACRO in makefiles: $(AUTO_CONFIGURE_TARGET) see my change to directfb.mk. New style Autotools.in will use it if you set the global option. However you can enable the global option and on a per package overrule it by doing the following: $(PKGNAME)_USE_CONFIG_CACHE = NO see fontconfig.mk for an example of this. Finally I have removed a few config variable settings which indicated no CXX compiler as this is wrong and breaks the build when using this central cache. Config.in | 8 ++++++++ package/Makefile.autotools.in | 5 ++++- package/Makefile.in | 28 +++++++++++++++++++++++++++- package/atk/atk.mk | 2 +- package/directfb/directfb.mk | 7 +------ package/fontconfig/fontconfig.mk | 3 +++ package/libglib2/libglib2.mk | 2 +- package/libgtk2/libgtk2.mk | 1 - 8 files changed, 45 insertions(+), 11 deletions(-) I would appreciate feedback on this change (I have been testing for 2-3 weeks) But I can never test all cases! If you enable the BR2_CONFIG_CACHE option some Makefile.autotools.in based packages may now break - I cannot build them all. In this case you may need to remove config options that are being hardcoded all over the place (like gtk saying we have 2 CXX compiler) or disable the use of CONFIG CACHE file like I have done in fontconfig. I can build all packages required to get WebKit on DirectFB up and running and it runs fine. I will try to resolve any issues this creates as fast as I can. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
2008-11-28 15:20:47 +01:00
FONTCONFIG_USE_CONFIG_CACHE = NO
updated fontconfig
2008-03-06 19:09:37 +01:00
FONTCONFIG_INSTALL_STAGING = YES
FONTCONFIG_INSTALL_TARGET = YES
Adding Central config.cache options The following changes allow for use of a central configure cache file. This speeds up configuration of packages. Its use is configurable at the top level (BR2_CONFIG_CACHE - default n). Old style makefiles can use it if they use the following MACRO in makefiles: $(AUTO_CONFIGURE_TARGET) see my change to directfb.mk. New style Autotools.in will use it if you set the global option. However you can enable the global option and on a per package overrule it by doing the following: $(PKGNAME)_USE_CONFIG_CACHE = NO see fontconfig.mk for an example of this. Finally I have removed a few config variable settings which indicated no CXX compiler as this is wrong and breaks the build when using this central cache. Config.in | 8 ++++++++ package/Makefile.autotools.in | 5 ++++- package/Makefile.in | 28 +++++++++++++++++++++++++++- package/atk/atk.mk | 2 +- package/directfb/directfb.mk | 7 +------ package/fontconfig/fontconfig.mk | 3 +++ package/libglib2/libglib2.mk | 2 +- package/libgtk2/libgtk2.mk | 1 - 8 files changed, 45 insertions(+), 11 deletions(-) I would appreciate feedback on this change (I have been testing for 2-3 weeks) But I can never test all cases! If you enable the BR2_CONFIG_CACHE option some Makefile.autotools.in based packages may now break - I cannot build them all. In this case you may need to remove config options that are being hardcoded all over the place (like gtk saying we have 2 CXX compiler) or disable the use of CONFIG CACHE file like I have done in fontconfig. I can build all packages required to get WebKit on DirectFB up and running and it runs fine. I will try to resolve any issues this creates as fast as I can. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
2008-11-28 15:20:47 +01:00
# This package does not like using the target cflags for some reason.
Get rid of a host-dependency.
2009-01-10 14:47:18 +01:00
FONTCONFIG_CONF_ENV = CFLAGS="-I$(STAGING_DIR)/usr/include/freetype2"
updated fontconfig
2008-03-06 19:09:37 +01:00
fontconfig: remove redundant configure args Patch by antialize / bug #4524.
2008-08-16 21:13:53 +02:00
FONTCONFIG_CONF_OPT = --with-arch=$(GNU_TARGET_NAME) \
- pass the freetype-config location to make and disable building docs. This package is broken since it passes TARGET_CFLAGS down to the HOSTCC in e.g. fc-case
2007-01-16 17:06:45 +01:00
--with-freetype-config="$(STAGING_DIR)/usr/bin/freetype-config" \
fontconfig: fix typo added in r25611
2009-03-12 00:30:29 +01:00
--with-cache-dir=/var/cache/fontconfig \
Make paths to expat available to fontconfig
2007-08-12 14:05:55 +02:00
--with-expat="$(STAGING_DIR)/usr/lib" \
--with-expat-lib=$(STAGING_DIR)/usr/lib \
--with-expat-includes=$(STAGING_DIR)/usr/include \
fontconfig: bump version
2008-06-26 16:04:39 +02:00
--disable-docs
add fontconfig package
2007-01-14 04:39:53 +01:00
updated fontconfig
2008-03-06 19:09:37 +01:00
FONTCONFIG_DEPENDENCIES = uclibc freetype expat
add fontconfig package
2007-01-14 04:39:53 +01:00
updated fontconfig
2008-03-06 19:09:37 +01:00
$(eval $(call AUTOTARGETS,package,fontconfig))
cairo: add host version
2009-03-18 22:22:04 +01:00
# fontconfig for the host
FONTCONFIG_HOST_DIR:=$(BUILD_DIR)/fontconfig-$(FONTCONFIG_VERSION)-host
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
$(STAMP_DIR)/host_fontconfig_unpacked: $(DL_DIR)/$(FONTCONFIG_SOURCE)
mkdir -p $(FONTCONFIG_HOST_DIR)
cairo: add host version
2009-03-18 22:22:04 +01:00
$(INFLATE$(suffix $(FONTCONFIG_SOURCE))) $< | \
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
$(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $(FONTCONFIG_HOST_DIR) $(TAR_OPTIONS) -
cairo: add host version
2009-03-18 22:22:04 +01:00
touch $@
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
$(STAMP_DIR)/host_fontconfig_configured: $(STAMP_DIR)/host_fontconfig_unpacked $(STAMP_DIR)/host_freetype_installed $(STAMP_DIR)/host_expat_installed
(cd $(FONTCONFIG_HOST_DIR); rm -rf config.cache; \
cairo: add host version
2009-03-18 22:22:04 +01:00
$(HOST_CONFIGURE_OPTS) \
CFLAGS="$(HOST_CFLAGS)" \
LDFLAGS="$(HOST_LDFLAGS)" \
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
./configure \
--prefix="$(HOST_DIR)/usr" \
--sysconfdir="$(HOST_DIR)/etc" \
cairo: add host version
2009-03-18 22:22:04 +01:00
--disable-docs \
--disable-static \
)
touch $@
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
$(STAMP_DIR)/host_fontconfig_compiled: $(STAMP_DIR)/host_fontconfig_configured
$(HOST_MAKE_ENV) $(MAKE) -C $(FONTCONFIG_HOST_DIR)
cairo: add host version
2009-03-18 22:22:04 +01:00
touch $@
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
$(STAMP_DIR)/host_fontconfig_installed: $(STAMP_DIR)/host_fontconfig_compiled
$(HOST_MAKE_ENV) $(MAKE) -C $(FONTCONFIG_HOST_DIR) install
touch $@
cairo: add host version
2009-03-18 22:22:04 +01:00
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
host-fontconfig: $(STAMP_DIR)/host_fontconfig_installed
cairo: add host version
2009-03-18 22:22:04 +01:00
host-fontconfig-source: fontconfig-source
host-fontconfig-clean:
package: add STAMP_DIR and use for host builds Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
2009-03-19 12:06:47 +01:00
rm -f $(addprefix $(STAMP_DIR)/host_fontconfig_,unpacked configured compiled installed)
cairo: add host version
2009-03-18 22:22:04 +01:00
-$(MAKE) -C $(FONTCONFIG_HOST_DIR) uninstall
-$(MAKE) -C $(FONTCONFIG_HOST_DIR) clean
host-fontconfig-dirclean:
rm -rf $(FONTCONFIG_HOST_DIR)
Reference in New Issue Copy Permalink