From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <martin.jansa@gmail.com>
Cc: <j.armandohernandez.j@gmail.com>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] how to reuse generated library in a nativesdk recipe #sdk #systemd
Date: Thu, 20 Feb 2020 08:14:04 +0000 [thread overview]
Message-ID: <20200220081404.GF104502@korppu> (raw)
In-Reply-To: <CA+chaQeh2s-T-qXABAkr_28Wp2UZe0-WkZCEOuZ52cnUYtQsfg@mail.gmail.com>
On Wed, Feb 19, 2020 at 10:57:41PM +0100, Martin Jansa wrote:
> > DEPENDS_class-target += "systemd"
>
> You surely meant
> DEPENDS_append_class-target = " systemd"
> here
Yes, quite likely. Tough reason why += doesn't work is a mystery to me :)
I hack things until "bitbake -e" shows the right things for the recipes.
-Mikko
> On Wed, Feb 19, 2020 at 10:48 PM Mikko Rapeli <mikko.rapeli@bmw.de> wrote:
>
> > Hi,
> >
> > On Wed, Feb 19, 2020 at 01:37:19AM -0800, Armando Hernandez wrote:
> > > Hello,
> > >
> > > I have a recipe that builds a library. The recipe specifies an
> > additional package "${PN}-systemd" along with other systemd related
> > variables and finally it instructs that the package should be built with
> > "-DWITH_SYSTEMD=ON" being passed to cmake. So far so good. But, I extended
> > this recipe to nativesdk because I need this library on it. When trying to
> > build the corresponding nativesdk package, the build fails at the
> > configuration step (i.e. "do_configure") claiming it cannot find the
> > package systemd.
> > >
> > > Is there a way I can install the -already-generated libraries into my
> > SDK (potentially via the corresponding nativesdk recipe) without having to
> > rebuild the package? Or do I need to somehow include such systemd package
> > in my sdk (which I don't think I need at all)?
> > >
> > > Any hints and pointers as to were to look at are very well appreciated.
> > > Thanks.
> >
> > Make the systemd dependency for target only, e.g. DEPENDS_class-target +=
> > "systemd"
> > etc.
> >
> > There may be relevant use cases to build some of systemd components or
> > tools
> > to native or nativesdk targets too. In that case add BBCLASSEXTEND +=
> > "nativesdk" etc
> > in a bbappend to systemd.
> >
> > Hope this helps,
> >
> > -Mikko
> >
next prev parent reply other threads:[~2020-02-20 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 9:37 how to reuse generated library in a nativesdk recipe #sdk #systemd Armando Hernandez
2020-02-19 9:44 ` [yocto] " Mikko Rapeli
[not found] ` <CAGpycA+PGsbqnJL1FD8pPNzWK3203RoBTPPD08Vwjn5J9aGMJA@mail.gmail.com>
2020-02-19 15:57 ` Mikko Rapeli
2020-02-19 21:57 ` Martin Jansa
2020-02-20 8:14 ` Mikko Rapeli [this message]
2020-02-20 11:55 ` Martin Jansa
2020-02-20 12:01 ` Mikko Rapeli
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=20200220081404.GF104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=j.armandohernandez.j@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox