From: <Mikko.Rapeli@bmw.de>
To: <wpdster@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: How to share files between recipes?
Date: Thu, 19 Sep 2019 13:48:20 +0000 [thread overview]
Message-ID: <20190919134820.GI6154@hiutale> (raw)
In-Reply-To: <CAF_dkJBpgkpBJMTueuiNFNEVDeLy6=ZowViJ-G4QzDBOx=qRZw@mail.gmail.com>
On Thu, Sep 19, 2019 at 09:39:32AM -0400, Patrick Doyle wrote:
> I have a set of data files (cryptographic keys) that I would like to
> share among several recipes in my build. They won't go into the
> rootfs, but they will be used by multiple recipes that construct the
> rootfs. So, to the best of my understanding, it seems like I should
> put them in sysroot and somehow access them from there.
One possibility is to provide these keys as host native tools and data to
build of target recipes. This makes the files available in the build environment
but does not expose them to target.
Create a -native recipe which has and installs the files and use via DEPENDS to
the -native recipe.
Hope this helps,
-Mikko
next prev parent reply other threads:[~2019-09-19 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 13:39 How to share files between recipes? Patrick Doyle
2019-09-19 13:45 ` Maciej Pijanowski
2019-09-19 13:48 ` Mikko.Rapeli [this message]
2019-09-19 14:03 ` Patrick Doyle
2019-09-19 14:00 ` Patrick Doyle
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=20190919134820.GI6154@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=wpdster@gmail.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.