Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
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:03:13 +0200	[thread overview]
Message-ID: <55B54B11.1090200@openwide.fr> (raw)
In-Reply-To: <20150726214700.68302c4a@free-electrons.com>

Thomas,

Le 26/07/2015 21:47, Thomas Petazzoni a ?crit :
> Hello,
> 
> On Sun, 26 Jul 2015 20:46:36 +0300, kyak wrote:
>> From: Mikhail Peselnik <bas@bmail.ru>
>>
>> These flags need to be set so that the configure script would
>> correctly use libICE from cross-toolchain rather than from host.
>> Also, the xterm package is missing the freetype2 dependency, as
>> noted by Romain Naour.
> 
> So it should be two patches.
> 
> Basically, if your patch does something that isn't summarized in the
> commit title, then probably something wrong is going on.
> 
> So, one patch for x-includes/x-libraries, one patch for the missing
> freetype2 dependency.
> 
> However, I believe Romain was maybe wrong: the freetype dependency
> seems to be optional, according to configure.in. So it should probably
> just be:
> 
> ifeq ($(BR2_PACKAGE_FREETYPE),y)
> XTERM_DEPENDENCIES += freetype
> XTERM_CONF_OPTS += --enable-freetype
> else
> XTERM_CONF_OPTS += --disable-freetype
> endif
> 
> Romain, can you confirm?

I don't know much the xterm package but indeed the freetype support seems
optional. However, it depends on libXft.

So I made this change:

# freetype support needs libXft, so enable it only when
# libxft package is selected.
# Note: freetype is automatically selected by libXft.
ifeq ($(BR2_PACKAGE_XLIB_LIBXFT),y)
XTERM_DEPENDENCIES += freetype xlib_libXft
XTERM_CONF_OPTS += --enable-freetype \
	--with-freetype-cflags="-I$(STAGING_DIR)/usr/include/freetype2" \
	--with-freetype-libs="-L$(STAGING_DIR)/usr/lib"
else
XTERM_CONF_OPTS += --disable-freetype
endif

It doesn't work when freetype-config is used directly with:
--with-freetype-config=$(STAGING_DIR)/usr/bin/freetype-config

Mikhail, can you resend an updated version with this change?

Best regards,
Romain

> 
> Best regards,
> 
> Thomas
> 

  reply	other threads:[~2015-07-26 21:03 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 [this message]
2015-07-26 21:25     ` Thomas Petazzoni
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=55B54B11.1090200@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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