Thanks for your answer.
I already have the ALLOW_EMPTY_${PN} = "1" in the recipe
What I still don't get is why the -dev gets installed but the -staticdev
doesn't, even though the dependency is satisfied (the empty pkg exists).
On 06/02/18 22:25, Robert Berger wrote:
Hi,
On 2018-02-06 14:53, Mircea Gliga wrote:
Hello,
I have a problem providing a static library in the SDK:
I have a recipe that builds a library. It outputs an -dev pkg with
the /usr/{include,lib} libs in it and a -staticdev pkg with the
static library.
The main pkg is empty, in my recipe I have added ALLOW_EMPTY_${PN} =
"1" because the -dev and -staticdev depend on it
In my local.conf I have added:
SDKIMAGE_FEATURES += "dev-pkgs dbg-pkgs staticdev-pkgs"
Then I run
bitbake my-image -c populate_sdk
After installing the SDK, I get the headers (from the -dev pkg) but
not the static library from the -staticdev pkg.
Why is that ? From my understanding specifying staticdev-pkgs in the
SDKIMAGE_FEATURE should have this covered.
I was able to "force" the install of the -staticdev pks by adding to
local.conf:
TOOLCHAIN_TARGET_TASK_append = " mylibrary-staticdev"
Do you have to manually take care of this ? Then, what's the purpose
of SDKIMAGE_FEATURES += " staticdev-pkgs" ?
I would like to have all static libraries in the SDK.
Thanks and regards
This sounds like:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11724
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto