From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/1] xterm: x-includes and x-libraries must be set for cross-compiling
Date: Sun, 26 Jul 2015 23:25:15 +0200 [thread overview]
Message-ID: <20150726232515.7e959c25@free-electrons.com> (raw)
In-Reply-To: <55B54B11.1090200@openwide.fr>
Romain,
On Sun, 26 Jul 2015 23:03:13 +0200, Romain Naour wrote:
> I don't know much the xterm package but indeed the freetype support seems
> optional. However, it depends on libXft.
No, I think it's not the way it works. What xterm calls "freetype" is
*not* freetype, it's libXft, i.e X Freetype. If you look at the
definition of CF_X_FREETYPE, it searches for xft, and never for
freetype.
> # freetype support needs libXft, so enable it only when
> # libxft package is selected.
> # Note: freetype is automatically selected by libXft.
Don't add this comment.
> ifeq ($(BR2_PACKAGE_XLIB_LIBXFT),y)
> XTERM_DEPENDENCIES += freetype xlib_libXft
Don't add the freetype dependency here.
> XTERM_CONF_OPTS += --enable-freetype \
> --with-freetype-cflags="-I$(STAGING_DIR)/usr/include/freetype2" \
> --with-freetype-libs="-L$(STAGING_DIR)/usr/lib"
I think these are wrong. Instead, do:
--with-freetype-config=auto
It will use pkg-config to find libXft. Of course, make sure
host-pkgconf is in the dependencies.
> It doesn't work when freetype-config is used directly with:
> --with-freetype-config=$(STAGING_DIR)/usr/bin/freetype-config
Yes, because it's not looking for freetype, but Xft.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-26 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 17:46 [Buildroot] [PATCHv2 1/1] xterm: x-includes and x-libraries must be set for cross-compiling kyak
2015-07-26 17:59 ` Yann E. MORIN
2015-07-26 19:37 ` Romain Naour
2015-07-26 19:44 ` Thomas Petazzoni
2015-07-26 20:02 ` Yann E. MORIN
2015-07-26 19:47 ` Thomas Petazzoni
2015-07-26 21:03 ` Romain Naour
2015-07-26 21:25 ` Thomas Petazzoni [this message]
2015-07-27 14:49 ` Romain Naour
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=20150726232515.7e959c25@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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