On Tue, 11 Dec 2001 19:33:25 -0500,
"Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]>:
>> >Is there a way we could split the help entries into arch specific entries ?
>> >like using config variables CONFIG_INSTALL_$ARCH_VMLINUX or something ?
>>
>> AFAICT, not in CML1. The CML1 help text is under the first entry on
>> the choice list. In CML2 each choice entry has its own help text.
>
>Not quite yet. CML2 still uses the CML1 convention. That will change
>after cutover.
It already works for me using cml2 1.9.6. The help text for the menu
item is one entry, the individual choices have separate text.
symbols
VMLINUX 'vmlinux' text
This is the raw format that is produced by the kernel build. It is
required to use any of the various source debugging tools on the kernel
itself and is the only bootable format on some architectures. It is
generally too large to be used otherwise.
Note that the `vmlinux' format is produced by ALL compilations, either
as the target step, or as an intermediate step in the production of one
of the other formats.
.
VMLINUZ 'vmlinuz' text
vmlinux after being stripped to remove debugging information then
compressed using gzip. This is still the same basic format as vmlinux,
just smaller.
.
.....
symbols
kernel_format_x86 'The format used for the installed kernel' text
All kernel builds create vmlinux as an ELF object. vmlinux may not be
suitable for loading, either because the bootloader cannot handle ELF
or the object is too large. This option selects the format for the
installed kernel. If unsure, use bzImage.
.
choices kernel_format_x86 # The format that the kernel is to be compiled in
VMLINUX VMLINUZ BZIMAGE ZIMAGE default BZIMAGE
menu installation
kernel_format_x86
unless x86 suppress kernel_format_x86
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
