Thanks for your reply Anooj. Apparently, based on my findings, the SDK contains libraries that are "libtool archives", .la. For my part, I have used .a only which is not "libtoolized". I'm finding a way how to make my unit generate a libtool archive.
- Joseph On Wed, Jul 23, 2014 at 3:18 PM, Anooj Gopi <anoojg...@gmail.com> wrote: > The package installed tmp/sysroot and your SDK sysroot are not same by > default. > You have to find in which package your .a files are. Adding it to > "TOOLCHAIN_HOST_TASK" may help. > I am not sure if this will help as I am currently through the similar > issues. > > > On Wed, Jul 23, 2014 at 5:20 AM, Joseph Andrew de la Peña < > jdelap...@lexmark.com> wrote: > >> Good day, >> >> I have bumped into a problem when compiling from my generated SDK (-c >> populate_sdk). I have archive libraries (.a) that were not reflected in my >> SDK's lib dir in sysroots. However, my shared objects (.so) are present. I >> needed both .a and .so to be present in my SDK. With the former being the >> problem, how can archive libraries be included in SDK? I've checked in my >> poky and all .a are installed successfully in tmp/sysroots. >> >> Thanks, >> Joseph >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >> >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto