We have an issue that certain libraries that we have added to our project are only landing in the SDK's sysroot if the packages that need them are either listed explicitly (and not only as dependency of another package) or if the library in question is listed as RDEPENDS, although this is not necessary to run the packages on the target.

I was then told that the SDK just holds a "minimal set of libraries" in the syroot. So only "some packages and libraries" land in the SDK and if I wanted to have all packages, I would have to use the eSDK. This is not clear from the documentation at all. From my understanding the only difference is that the eSDk also contains tools like devtool and the SDK supports a traditional workflow. There is nothing stating that the sysroot of the SDK is incomplete or what it actually contains.

I also think that the SDK should contain our custom libraries. Maybe there is a bug that I have to add the library as RDEPENDS.