Hi Joseph,
On Monday 11 August 2014 13:49:52 Joseph Andrew de la Peña wrote:
Still can't find the solution to include archive libraries into SDK. I have
already checked staticdev and my unit is already using it. The archive libs
are installed successfully in the image's sysroot but apparently
Good day Paul,
Yes, it worked. I can see my archive libs now. BUT one last problem, there
are few units publishing archive libs that were not included. What would I
need to add in my recipe to those units for it to work?
Apparently, I have my own meta-layer, and I put the SDKIMAGE_FEATURES in
On Monday 11 August 2014 20:17:31 Joseph Andrew de la Peña wrote:
Yes, it worked. I can see my archive libs now. BUT one last problem, there
are few units publishing archive libs that were not included. What would I
need to add in my recipe to those units for it to work?
That should not be the
Good day Yocto Dev Community,
Still can't find the solution to include archive libraries into SDK. I have
already checked staticdev and my unit is already using it. The archive libs
are installed successfully in the image's sysroot but apparently not in
sdk. Hope you could shed some light here.
Good day Ross,
I've mimic'd the bitbake.conf way of adding -staticdev. Apparently I got a
QA error stating that there are already multiple definitions of -staticdev
for my unit.
BTW, what's the purpose of ALLOW_EMPTY_${PN} = 1 and
ALLOW_EMPTY_${PN}-dev = 1?
Really thank you for your help with
On 24 July 2014 08:30, Joseph Andrew de la Peña jdelap...@lexmark.com wrote:
I've mimic'd the bitbake.conf way of adding -staticdev. Apparently I got a
QA error stating that there are already multiple definitions of -staticdev
for my unit.
Your package will already have them due to the default
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
On 23 July 2014 10:23, Joseph Andrew de la Peña jdelap...@lexmark.com wrote:
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
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
