On 13-04-08 04:54 PM, Richard Purdie wrote: > On Mon, 2013-04-08 at 16:15 -0400, [email protected] wrote: >> From: Michel Thebeau <[email protected]> >> >> Allow recipes to specify sections to be stripped from the kernel output >> using KERNEL_IMAGE_STRIP_EXTRA_SECTIONS. For example: >> >> KERNEL_IMAGE_STRIP_EXTRA_SECTIONS = ".comment .unwanted" >> >> The file to be stripped is a copy of ${KERNEL_OUTPUT} and will be given >> the same name with an additional ".stripped" suffix. The suffix can be >> overridden using KERNEL_STRIP_SUFFIX. >> >> Since the toolchain does not give indication when the specified sections >> are absent, we read the sections first and make this report by issuing a >> warning to the developer. >> >> The toolchain by default strips the image with the -s option (even >> when -s is not specified): >> -s --strip-all Remove all symbol and relocation information >> >> For example, these sections are always removed: >> .debug_aranges >> .debug_info >> .debug_abbrev >> .debug_line >> .debug_frame >> .debug_str >> .debug_loc >> .debug_ranges >> .symtab >> .strtab >> >> In addition to these, the sections listed in >> KERNEL_IMAGE_STRIP_EXTRA_SECTIONS will also be removed. >> >> Only stripping of vmlinux (elf) is supported at this time. A warning >> will be given if the image type is not vmlinux. >> >> Stripping the image could also be done in the kernel, but that would >> only work for linux-yocto based kernels, so it's not the route we >> decided to go. >> >> [YOCTO 3515] >> >> Signed-off-by: Bruce Ashfield <[email protected]> >> Signed-off-by: Michel Thebeau <[email protected]> > > Can we please just have one output kernel, not two. Is the unstripped > version useful anywhere? >
The unstripped image is bootable, and it is conceivable that someone may even want to do load -m tftp from the boot script. But, if a single image is desirable then I'd go with the image stripped in place. Here is that other patch... I'll make sure to add text to the log so it is clear about what happened to the image. M > Cheers, > > Richard > > > _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
