From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: how to build boost_python module
Date: Wed, 01 Apr 2015 14:28:42 -0600 [thread overview]
Message-ID: <551C54FA.4010206@mlbassoc.com> (raw)
In-Reply-To: <60F6FAE47D1BCE4380CC06D18F49789BB9B55D6B@NTXBOIMBX02.micron.com>
On 2015-04-01 14:08, Andy Falanga (afalanga) wrote:
> Hi,
>
> I'm truly new to embedded systems development so please forgive my ignorance. I'm working on building an embedded Linux image (of course). In order to build the software that I'm interested to build for this ARM system (Zynq zc706), I need to build the python interpreter and the Boost libraries. I've found recipes for these in the system and have used Hob to try to make this happen. Thus far, no matter what I've tried, I don't see boost_python built. Currently, in the Hob interface, I'm selecting packages to build into the image and boost-python isn't listed. The boost.inc file in /opt/yocto/poky-dizzy-12.0.1/meta/recipes-support/boost shows logic to build boost-python. Since python is being built into this image, shouldn't this package have been built too?
>
> The question is a simple one, how do I get the build to make boost-python? It's made all of the others I need for my own library: boost-thread, boost-regex, boost-filesystem, etc. I just can't get it to build boost-python.
>
This feature is controlled by package config in the boost recipe.
Adding this line to your local.conf should get it built.
PACKAGECONFIG_pn-boost = "python"
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-04-01 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 20:08 how to build boost_python module Andy Falanga (afalanga)
2015-04-01 20:28 ` Gary Thomas [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=551C54FA.4010206@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 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.