From: Patrick Ohly <patrick.ohly@intel.com>
To: "thilo.cestonaro@ts.fujitsu.com" <thilo.cestonaro@ts.fujitsu.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Using boost-program-options and native
Date: Thu, 13 Apr 2017 08:34:05 +0200 [thread overview]
Message-ID: <1492065245.27604.45.camel@intel.com> (raw)
In-Reply-To: <1492004877.5507.2.camel@ts.fujitsu.com>
On Wed, 2017-04-12 at 13:47 +0000, thilo.cestonaro@ts.fujitsu.com wrote:
> Hey all!
>
> I want to build a tool which makes use of boost-program-options lib. As long as I compile for the target, all is fine, but when I add
> > BBCLASSEXTEND += "native"
> to my recipe, I a bitbake error "Nothing Provides" ... :(
>
> > ERROR: Required build target 'mytool-native' has no buildable providers.
> > Missing or unbuildable dependency chain was: ['mytool-native', 'boost-program-options-native']
>
> In the recipe I just depend on boost and RDEPEND on boost-program-options:
> > DEPENDS = "boost"
> > RDEPENDS_${PN} = "boost-program-options"
>
> Is something wrong with this? Why is there a package
> boost-program-options but no boost-program-options-native, altough
> boost-native exists and the libboost-program-options.so is installed
> into the
> native sysroot. (I can compile flawlessly without the RDEPENDS line.)
Native and nativesdk flavors don't have packages, so RDEPENDS only works
when depending on ${PN}-native (but not for ${PN}-native-some-package).
Try:
DEPENDS = "boost"
RDEPENDS_${PN}_class-target = "boost-program-options"
"boost" already is a dependency via DEPENDS, so you shouldn't need an
RDEPENDS for it in the native case.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-04-13 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 13:47 Using boost-program-options and native thilo.cestonaro
2017-04-13 6:34 ` Patrick Ohly [this message]
2017-04-13 6:53 ` Phil Wise
2017-04-13 7:26 ` thilo.cestonaro
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=1492065245.27604.45.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thilo.cestonaro@ts.fujitsu.com \
/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