write a tool to fix the libtool .la files so that they do not call other .la files but are calling the real libraries that way we can avoid lot of overlinking.
Ross has a preliminary class here https://github.com/rossburton/meta-ross/blob/master/classes/wipe-la.bbclass
It would be good to prioritize this bug, because now overlinking is manifesting itself in misleading error messages of devtool (a part of extended SDK) like NOTE: gupnp: compiling from external source tree /home/rojkov/files/repos/gupnp ERROR: QA Issue: gssdp rdepends on libxml2, but it isn't a build dependency? [build-deps] ERROR: QA Issue: gssdp rdepends on zlib, but it isn't a build dependency? [build-deps] ERROR: QA Issue: gssdp rdepends on libsqlite3, but it isn't a build dependency? [build-deps] ERROR: QA Issue: gssdp rdepends on libffi, but it isn't a build dependency? [build-deps]
Is something like wipe-la still a viable candidate here?
Do we want an optional class or should it just be an intrinsic part of our build process?
I'm tempted to say default to on but able to be disabled, just in case someone has a situation where they actually need .la files.
For what it's worth, gnome-continuous (yocto-based CI for GNOME) does this in it's bootstrap image generation: find ${IMAGE_ROOTFS}/usr/lib -name \*.la -delete And then in each "recipe" build, just deletes every .la file after install. Maybe we should try with just deleting them before packaging.
I just posted remove-libtool.bbclass to the list. This isn't enabled by default but will remove *all* libtool .la files from both target packages and sysroot, so libtool can't go crazy.
Merged in oe-core da1219b5c48fe50d667bc72bd9ad0115b25d5558.
Ross, I added this class to the ref manual: file:///home/scottrif/yocto-docs/documentation/ref-manual/ref-manual.html#ref-classes-remove-libtool. Let me know if this is okay and I will reset the doc flag to "done." Scott
Looks good to me, thanks Scott. Setting flag to 'done'.