Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
To: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: set up PACKAGECONFIG for boost-python library
Date: Mon, 23 Sep 2013 07:47:33 +0200	[thread overview]
Message-ID: <523FD5F5.1000209@oss.bmw-carit.de> (raw)
In-Reply-To: <1379307553-2744-1-git-send-email-lukas.bulwahn@oss.bmw-carit.de>

On 09/16/2013 06:59 AM, Lukas Bulwahn wrote:
> Until now, the comment in the boost.inc file suggested to enable
> the boost-python library by uncommenting some lines in that file.
> Using the new PACKAGECONFIG feature, boost-python can now be added
> optionally without need to modify the file or copying those lines
> into a bbappend file.
> Furthermore, we obtain the python version by inheriting python-dir
> instead of fixing the python version in this file.
>
> This commit is motivated by the need in the meta-ros layer, as
> discussed in the issue #145 of the meta-ros issue tracker [1].
>
> [1] https://github.com/bmwcarit/meta-ros/pull/145
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
> ---
>   meta/recipes-support/boost/boost.inc |   15 ++++++++-------
>   1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
> [...]
This patch has been pending since last Monday. Are there any general 
concerns about this patch or has it been simply overlooked?

Yours sincerely,

Lukas Bulwahn


      reply	other threads:[~2013-09-23  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16  4:59 [PATCH] boost: set up PACKAGECONFIG for boost-python library Lukas Bulwahn
2013-09-23  5:47 ` Lukas Bulwahn [this message]

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=523FD5F5.1000209@oss.bmw-carit.de \
    --to=lukas.bulwahn@oss.bmw-carit.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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