From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libxml2: add support for building host library with python support
Date: Wed, 14 Nov 2012 10:25:45 +0100 [thread overview]
Message-ID: <20121114102545.7f835367@skate> (raw)
In-Reply-To: <1352883977-16288-1-git-send-email-noel.vellemans@visionbms.com>
Noel,
On Wed, 14 Nov 2012 10:06:17 +0100, Noel vellemans wrote:
> +config BR2_PACKAGE_HOST_LIBXML2_PYTHON
> + bool
> \ No newline at end of file
I don't know if we want to introduce sub-options for host packages.
> diff --git a/package/libxml2/libxml2.mk b/package/libxml2/libxml2.mk
> index 71f2bd1..fde3735 100644
> --- a/package/libxml2/libxml2.mk
> +++ b/package/libxml2/libxml2.mk
> @@ -26,7 +26,15 @@ LIBXML2_POST_INSTALL_STAGING_HOOKS +=
> LIBXML2_STAGING_LIBXML2_CONFIG_FIXUP
> HOST_LIBXML2_DEPENDENCIES = host-pkgconf
>
> -HOST_LIBXML2_CONF_OPT = --without-debug --without-python
> +HOST_LIBXML2_CONF_OPT = --without-debug
> +
> +ifeq ($(BR2_PACKAGE_HOST_LIBXML2_PYTHON),y)
> +HOST_LIBXML2_DEPENDENCIES += host-python
> +HOST_LIBXML2_CONF_OPT += --with-python=$(HOST_DIR)/usr
> +else
> +HOST_LIBXML2_CONF_OPT += --without-python
> +endif
I'm confused here. I thought mesa required a Python that has xml2
support. But here you're building xml2 with Python support. Could you
enlighten me? :-)
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-14 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 9:06 [Buildroot] [PATCH 1/1] libxml2: add support for building host library with python support Noel vellemans
2012-11-14 9:25 ` Thomas Petazzoni [this message]
2012-11-14 9:53 ` Vellemans, Noel
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=20121114102545.7f835367@skate \
--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