I'm building obmc-phosphor-image for example, and what I found I had to do was to go to obmc-phosphor-image-base.inc, for me I was trying to use the eSDK exactly as it's described, building application level programs, so for me I needed curl, libz, etc.
What I found that I had to do(open to a better, more good practice way...) :
1) Modify DEPENDS:append = " obmc-phosphor-nor-image" into DEPENDS:append = " obmc-phosphor-nor-image openssl zlib curl libxcrypt "
2) Add TOOLCHAIN_TARGET_TASK:append = " libxcrypt libxcrypt-dev"
I could then build the eSDK, build my applications, and the linker found everything it needed to complete. This is a bit of a conflated example because libcrypt(yes, libcrypt without the x) is just weird, but it shows that even adding a library is not straight forward in yocto. So don't be frustrated if you are.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.