On Thu, 2021-01-14 at 08:06 +0000, Diego Sueiro wrote:
> The intermediate-deploy class is to be inherited by recipes that
> install intermediate artifacts which are not present in the filesystem
> to be further processed by other recipes.
>
> The INTERMEDIATE_DEPLOY_DIRS variable is a space separated list of dirnames
> from ${D} which include the intermediate artifacts.
>
> Change-Id: I314987587c1cf0e4cdb28fbf11463f1feb37504b
> ---
> meta/classes/intermediate-deploy.bbclass | 25 ++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
> create mode 100644 meta/classes/intermediate-deploy.bbclass
I think I should have been clearer about what I was thinking, sorry.
I was wondering about an "intermediate-deploy" directory within the
existing SYSROOT_DIRS, so the sysroot could contain an "intermediate-
deploy/boot/" and "intermediate-deploy/firmware".
I'm not particularly liking the name. Maybe "unpackaged/boot" or "non-
target/boot"? I'm open to ideas.
The idea is to make it really clear these are files which are not part
of the target rootfs though...
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#146681):
https://lists.openembedded.org/g/openembedded-core/message/146681
Mute This Topic: https://lists.openembedded.org/mt/79671196/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
