As target binaries and libraries are now built with extra debugging symbols, some of the -dbg packages are very large. Unfortunately, -dbg packages only contain debug versions of executable binaries and shared libraries, but not static libraries, which go directly into -dev packages. That increases the size of sdk/toolchain tarballs, which include -dev packages, depending on the main packages, and end up with stripped shared libs, but bloated static libs.
I understand, that -dev packages are specifically for development and having full debugging symbols in a library might be helpful for that, but -dev packages don't usually depend on -dbg, and most toolchain-target tasks don't include them either, hence not providing debugging versions of shared libs in the sdk/toolchain. Would it make sense to package stripped version of a static lib into -dev and the full version into corresponding -dbg? -- Denys _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
