On 13-06-09 18:44, Koen Kooi wrote:
Hi,There was a recent thread on the OE-devel mailinglist about making our -dbg packages a bit more usefull, so I tried this: -FULL_OPTIMIZATION = "-fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os" +FULL_OPTIMIZATION = "-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2 -ggdb3" -BUILD_OPTIMIZATION = "-Os" +BUILD_OPTIMIZATION = "-O2 -ggdb3" Using -ggdb3 will give us this: "Level 3 includes extra information, such as all the macro definitions present in the program. GDB supports macro expansion when you use `-gdb3'." A randomly picked sample recipe gives us: without -ggdb3 6204 KiB ipk/armv7a/gimp_2.6.3-r2.2_armv7a.ipk 924 KiB ipk/armv7a/gimp-dbg_2.6.3-r2.2_armv7a.ipk with -ggdb3 6220 KiB ipk/armv7a/gimp_2.6.3-r2.2_armv7a.ipk 95592 KiB ipk/armv7a/gimp-dbg_2.6.3-r2.2_armv7a.ipk So we get a small size increase (which might be due to going to O2) in ${PN} and a *hundredfold* size increase in the -dbg package.
And it turns out that taking gimp as example was the wrong thing to do :) Rebuilding everything from scratch shows that the package sizes stay the same, but that only the gimp package fluctuates a few KiB.
regards, Koen _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
