From: "Koeller, Thomas" <Thomas.Koeller@baslerweb.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: -staticdev packages not in sdk
Date: Tue, 6 Aug 2019 14:04:41 +0000 [thread overview]
Message-ID: <1565100281929.57461@baslerweb.com> (raw)
Hi,
browsing the list archives I came across an older thread that exactly describes the problem I am currently struggling with:
https://lists.yoctoproject.org/pipermail/yocto/2018-February/039950.html
In short, I have a recipe that produces only a couple of header files and a single static library, nothing to be installed on the target. So the base package is empty, which is why I have 'ALLOW_EMPTY_${PN} = "1"' in its recipe. In my image definition I have 'SDKIMAGE_FEATURES_append = " staticdev-pkgs"', so I expect the -staticdev package to be included when generating the SDK. This is, however, not the case. While a large number of -staticdev packages from different recipes is now included in the SDK, only the -dev package is included for my recipe, not the -staticdev (though the corresponding rpm is actually built and contains the library as expected, it just is not installed).
The archived mail thread referenced above suggests adding the base package ${PN} to IMAGE_INSTALL, which indeed does work for me. However, I do not understand why this is necessary at all, as my package is already referenced from another recipe by being listed in that recipe's DEPENDS variable, shouldn't that be enough? Also, the -dev package gets installed into the SDK even without such cruft. As far as I can see, identical logic is applied to both -dev and -staticdev packages, so what is the difference?
I also found a different workaround for the problem: listing the -staticdev package in TOOLCHAIN_TARGET_TASK. Needless to say, this workaround is just as undesirable as the former one.
I am using the sumo branch.
Thomas
Thomas Koeller
Senior Software Developer
Basler AG
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel. +49 4102 463 390
Fax +49 4102 463 46 390
Thomas.Koeller@baslerweb.com
www.baslerweb.com
Management board: Dr.-Ing. Dietmar Ley (CEO) · John P. Jennings · Arndt Bake · Hardy Mehl
Chairman of the supervisory board: Norbert Basler
Basler AG · Amtsgericht Lübeck HRB 4090 · Ust-IdNr.: DE 135 098 121 · Steuer-Nr.: 30 292 04497 · WEEE-Reg.-Nr. DE 83888045
next reply other threads:[~2019-08-06 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 14:04 Koeller, Thomas [this message]
2019-08-06 22:06 ` -staticdev packages not in sdk Richard Purdie
2019-08-07 9:06 ` Koeller, Thomas
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=1565100281929.57461@baslerweb.com \
--to=thomas.koeller@baslerweb.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.