Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Lockenvitz <l.lockenvitz@fpga-art.de>
To: buildroot@busybox.net
Subject: [Buildroot] no fontconfig in $(TARGET_DIR)
Date: Thu, 30 Jul 2009 16:06:00 +0200	[thread overview]
Message-ID: <4A71A8C8.5030409@fpga-art.de> (raw)

Hello,

I don't use the newest buildroot version. I use rev 25671 from git.
And have the problem that fontconfig is present in $(STAGING_DIR) but 
not in $(TARGET_DIR).
But the fontconfig.mk says:

FONTCONFIG_VERSION = 2.6.0
FONTCONFIG_SOURCE = fontconfig-$(FONTCONFIG_VERSION).tar.gz
FONTCONFIG_SITE = http://fontconfig.org/release
FONTCONFIG_AUTORECONF = YES
FONTCONFIG_USE_CONFIG_CACHE = NO
FONTCONFIG_INSTALL_STAGING = YES
FONTCONFIG_INSTALL_TARGET = YES
# This package does not like using the target cflags for some reason.
FONTCONFIG_CONF_ENV = CFLAGS="-I$(STAGING_DIR)/usr/include/freetype2"

FONTCONFIG_CONF_OPT = --with-arch=$(GNU_TARGET_NAME) \
        --with-freetype-config="$(STAGING_DIR)/usr/bin/freetype-config" \
        --with-cache-dir=/var/cache/fontconfig \
        --with-expat="$(STAGING_DIR)/usr/lib" \
        --with-expat-lib=$(STAGING_DIR)/usr/lib \
        --with-expat-qincludes=$(STAGING_DIR)/usr/include \
        --disable-docs

FONTCONFIG_DEPENDENCIES = uclibc freetype expat

$(eval $(call AUTOTARGETS,package,fontconfig))

I can't see any error for this or something that let me know what the 
problem.
Is there a known problem or do someone a suggestion?

Regard
Lars

             reply	other threads:[~2009-07-30 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 14:06 Lars Lockenvitz [this message]
2009-07-31  7:16 ` [Buildroot] no fontconfig in $(TARGET_DIR) Peter Korsgaard
     [not found]   ` <4A72BD91.7040703@fpga-art.de>
2009-07-31  9:52     ` Peter Korsgaard

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=4A71A8C8.5030409@fpga-art.de \
    --to=l.lockenvitz@fpga-art.de \
    --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