From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] boost: make build with python an option
Date: Tue, 4 Mar 2014 10:42:55 +0200 [thread overview]
Message-ID: <20140304084255.GZ3874@tarshish> (raw)
In-Reply-To: <E1CF8EFE2042404B87DE2B6D662128020ED58B9D@KUUMEX10.barco.com>
Hi Johan,
On Tue, Mar 04, 2014 at 08:32:56AM +0000, Derycke, Johan wrote:
> Add an option to boost to build the Boost.Python library.
> http://www.boost.org/doc/libs/1_55_0/libs/python/doc/index.html
>
> Signed-off-by: Johan Derycke <johan.derycke@barco.com>
> ---
> package/Config.in | 1 +
> package/boost/Config.in | 4 ++++
> package/boost/boost.mk | 13 +++++++++++--
> 3 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/package/Config.in b/package/Config.in
> index 6edf18e..47e345a 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -442,6 +442,7 @@ source "package/python-id3/Config.in"
> source "package/python-ipy/Config.in"
> source "package/python-json-schema-validator/Config.in"
> source "package/python-keyring/Config.in"
> +source "package/python-libconfig/Config.in"
This hunk should move to the previous patch.
baruch
> source "package/python-mad/Config.in"
> source "package/python-meld3/Config.in"
> source "package/python-msgpack/Config.in"
> diff --git a/package/boost/Config.in b/package/boost/Config.in
> index 68c3909..a4fb745 100644
> --- a/package/boost/Config.in
> +++ b/package/boost/Config.in
> @@ -60,6 +60,10 @@ config BR2_PACKAGE_BOOST_MPI
> config BR2_PACKAGE_BOOST_PROGRAM_OPTIONS
> bool "boost-program_options"
>
> +config BR2_PACKAGE_BOOST_PYTHON
> + depends on BR2_PACKAGE_PYTHON
> + bool "boost-python"
> +
> config BR2_PACKAGE_BOOST_RANDOM
> bool "boost-random"
>
> diff --git a/package/boost/boost.mk b/package/boost/boost.mk
> index 7aab614..53d2b4d 100644
> --- a/package/boost/boost.mk
> +++ b/package/boost/boost.mk
> @@ -26,7 +26,7 @@ HOST_BOOST_FLAGS = --without-icu \
> # atomic library compile only with upstream version, wait for next release
> # coroutine breaks on some weak toolchains and it's new for 1.54+
> # log breaks with some toolchain combinations and it's new for 1.54+
> -BOOST_WITHOUT_FLAGS = atomic coroutine log python
> +BOOST_WITHOUT_FLAGS = atomic coroutine log
>
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_CHRONO),,chrono)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_CONTEXT),,context)
> @@ -40,6 +40,7 @@ BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_LOCALE),,locale)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_MATH),,math)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_MPI),,mpi)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_PROGRAM_OPTIONS),,program_options)
> +BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_PYTHON),,python)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_RANDOM),,random)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_REGEX),,regex)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_SERIALIZATION),,serialization)
> @@ -50,6 +51,8 @@ BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_THREAD),,thread)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_TIMER),,timer)
> BOOST_WITHOUT_FLAGS += $(if $(BR2_PACKAGE_BOOST_WAVE),,wave)
>
> +BOOST_TARGET_CXXFLAGS = $(TARGET_CXXFLAGS)
> +
> ifeq ($(BR2_PACKAGE_ICU),y)
> BOOST_FLAGS += --with-icu=$(STAGING_DIR)/usr
> BOOST_DEPENDENCIES += icu
> @@ -61,6 +64,12 @@ ifeq ($(BR2_PACKAGE_BOOST_IOSTREAMS),y)
> BOOST_DEPENDENCIES += bzip2 zlib
> endif
>
> +ifeq ($(BR2_PACKAGE_BOOST_PYTHON),y)
> +BOOST_FLAGS += --with-python-root=$(HOST_DIR)
> +BOOST_TARGET_CXXFLAGS += -I$(STAGING_DIR)/usr/include/python$(PYTHON_VERSION_MAJOR)/
> +BOOST_DEPENDENCIES += python
> +endif
> +
> HOST_BOOST_OPT += toolset=gcc threading=multi variant=release link=shared \
> runtime-link=shared
>
> @@ -84,7 +93,7 @@ BOOST_FLAGS += $(if $(BOOST_WITHOUT_FLAGS_COMMASEPERATED), --without-libraries=$
>
> define BOOST_CONFIGURE_CMDS
> (cd $(@D) && ./bootstrap.sh $(BOOST_FLAGS))
> - echo "using gcc : $(TARGET_CC_VERSION) : $(TARGET_CXX) : <cxxflags>\"$(TARGET_CXXFLAGS)\" <linkflags>\"$(TARGET_LDFLAGS)\" ;" > $(@D)/user-config.jam
> + echo "using gcc : $(TARGET_CC_VERSION) : $(TARGET_CXX) : <cxxflags>\"$(BOOST_TARGET_CXXFLAGS)\" <linkflags>\"$(TARGET_LDFLAGS)\" ;" > $(@D)/user-config.jam
> echo "" >> $(@D)/user-config.jam
> endef
>
> --
> 1.7.10.4
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-03-04 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 8:32 [Buildroot] [PATCH 2/2] boost: make build with python an option Derycke, Johan
2014-03-04 8:42 ` Baruch Siach [this message]
2014-03-04 8:54 ` Thomas Petazzoni
2014-03-04 9:34 ` Samuel Martin
2014-03-04 9:31 ` Samuel Martin
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=20140304084255.GZ3874@tarshish \
--to=baruch@tkos.co.il \
--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