From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] xterm: x-includes and x-libraries must be set for cross-compiling
Date: Mon, 27 Jul 2015 17:01:15 +0200 [thread overview]
Message-ID: <55B647BB.70000@openwide.fr> (raw)
In-Reply-To: <1438008410-1465-1-git-send-email-bas@bmail.ru>
Hi Mikhail,
Le 27/07/2015 16:46, Mikhail Peselnik a ?crit :
> These flags need to be set so that the configure script would
> correctly use libICE from cross-toolchain rather than from host.
>
> This fix is similar to "package/efl/libevas: x-includes and x-libraries
> must be set for cross-compiling" done by Romain Naour on libecore.
>
> Signed-off-by: Mikhail Peselnik <bas@bmail.ru>
Reviewed-by: Romain Naour <romain.naour@openwide.fr>
Best regards,
Romain
> ---
> package/xterm/xterm.mk | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/package/xterm/xterm.mk b/package/xterm/xterm.mk
> index 56f692d..778b40c 100644
> --- a/package/xterm/xterm.mk
> +++ b/package/xterm/xterm.mk
> @@ -10,6 +10,8 @@ XTERM_SITE = ftp://invisible-island.net/xterm
> XTERM_DEPENDENCIES = ncurses xlib_libXaw
> XTERM_LICENSE = MIT
> XTERM_LICENSE_FILES = version.c
> -XTERM_CONF_OPTS = --enable-256-color
> +XTERM_CONF_OPTS = --enable-256-color \
> + --x-includes=$(STAGING_DIR)/usr/include \
> + --x-libraries=$(STAGING_DIR)/usr/lib
>
> $(eval $(autotools-package))
>
next prev parent reply other threads:[~2015-07-27 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 14:46 [Buildroot] [PATCH 1/2] xterm: x-includes and x-libraries must be set for cross-compiling Mikhail Peselnik
2015-07-27 14:46 ` [Buildroot] [PATCH 2/2] package/xterm: compile with libXft support when it selected Mikhail Peselnik
2015-07-27 15:04 ` Romain Naour
2015-07-27 15:01 ` Romain Naour [this message]
2015-07-27 20:55 ` [Buildroot] [PATCH 1/2] xterm: x-includes and x-libraries must be set for cross-compiling Thomas Petazzoni
2015-07-28 4:38 ` kyak
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=55B647BB.70000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.