All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <j.armandohernandez.j@gmail.com>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] how to reuse generated library in a nativesdk recipe #sdk #systemd
Date: Wed, 19 Feb 2020 15:57:21 +0000	[thread overview]
Message-ID: <20200219155721.GD104502@korppu> (raw)
In-Reply-To: <CAGpycA+PGsbqnJL1FD8pPNzWK3203RoBTPPD08Vwjn5J9aGMJA@mail.gmail.com>

Hi,

(lets keep this on the list too)

On Wed, Feb 19, 2020 at 04:51:18PM +0100, Armando Hernandez wrote:
> Hi Mikko,
> 
> Thanks for your reply. I checked your suggestion but does not work for me.
> I did included a .bbappend file in which I:
> 
>    - re-set EXTRA_OECMAKE to an empty string (i.e. ""). - my intention was
>    to pass no arguments when building the nativesdk. Now I know that this
>    accion overwrites the value of EXTRA_OECMAKE in the original .bb file
>    - added the line BBCLASSEXTEND = "nativesdk" to this new .bbappend file
>    - added the line DEPENDS_class-target += "systemd" to the original .bb
>    file
> 
> I found out that this configures both the target and the nativesdk
> libraries without systemd - which later on causes a failure when bitbake
> attempts to pull up everything to create the final image.
> 
> Basically, I'd like to find a way to unset or overwrite the following
> variables when building the nativesdk package:
> 
>    - SYSTEMD_PACKAGES
>    - SYSTEMD_SERVICE_${PN}
>    - SYSTEMD_AUTO_ENABLE_${PN}
>    - SYSTEMD_SERVICE_${PN}-systemd
>    - SYSTEMD_AUTO_ENABLE_${PN}-systemd
>    - EXTRA_OECMAKE

You can add _class-[target|native|nativesdk] to all variables
to override defaults.

Verify with "bitbake -e".

Hope this helps,

-Mikko

> Is it possible to do so? Or do I come up with another recipe of the sama
> package exclusively for the nativesdk?
> 
> Thanks again.
> 
> Armando Hernandez
> 
> On Wed, Feb 19, 2020 at 10:44 AM <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

  parent reply	other threads:[~2020-02-19 22:01 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 [this message]
2020-02-19 21:57   ` Martin Jansa
2020-02-20  8:14     ` Mikko Rapeli
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=20200219155721.GD104502@korppu \
    --to=mikko.rapeli@bmw.de \
    --cc=j.armandohernandez.j@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 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.