On Thu, 2009-09-17 at 13:01 +0100, Phil Blundell wrote: > On Thu, 2009-09-17 at 01:40 -0400, Denys Dmytriyenko wrote: > > Would it make sense to package stripped version of a static lib into -dev > > and > > the full version into corresponding -dbg? > > I'm not sure that you'd want the debugging .a file in -dbg itself, since > the -dbg packages are for installation on the target device and the .a > libraries would be useless there. > > Punting the debug versions of the .a libraries into a new package > (-static-dbg or some such) wouldn't be a bad idea. Or, for SDK > purposes, you could even consider ditching the .a libraries altogether > for packages that have a .so since virtually nobody is going to be doing > static linking in this day and age. I often do static linking for different reasons: *different libc on the target(like with android for instance) *debugging(like in the case where all shared libs segfaulted on mips +uclibc,I needed a static gdb,a static strace etc...) Denis
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
