aboutsummaryrefslogtreecommitdiffstats
path: root/menu/README
diff options
context:
space:
mode:
authorMurali Krishnan Ganapathy <gmurali@cs.uchicago.edu>2005-12-16 16:25:49 -0600
committerH. Peter Anvin <hpa@zytor.com>2005-12-16 14:29:04 -0800
commita22c4aff0e5649fa22bbb4b7fda9433d7a8c44de (patch)
tree9f1c365dfc9b7174b31fbc7c769faf9bf8a57d0c /menu/README
parent1afe52436215236ac88a7c523d779fb2cf4cbd2a (diff)
downloadsyslinux-elf-a22c4aff0e5649fa22bbb4b7fda9433d7a8c44de.tar.gz
syslinux-elf-a22c4aff0e5649fa22bbb4b7fda9433d7a8c44de.tar.xz
syslinux-elf-a22c4aff0e5649fa22bbb4b7fda9433d7a8c44de.zip
advanced menu patch
Python code to generate C code from ini-like file format and changes to libmenu to accomodate a one pass parser. Diff is against 3.20-pre3 - Murali
Diffstat (limited to 'menu/README')
-rw-r--r--menu/README8
1 files changed, 6 insertions, 2 deletions
diff --git a/menu/README b/menu/README
index 66116e9c..aa979ed5 100644
--- a/menu/README
+++ b/menu/README
@@ -8,8 +8,12 @@ original author.
To configure the menus, you need to set up a menu configuration file
to have the menu items you desire, then build the menu system using
make. You can use either simple.c or complex.c as a starting point
-for your own menu configuration file; then add the name with a .c32
-extension to the MENUS list in the Makefile.
+for your own menu configuration file; If your menu system is only going
+to have entries corresponding to things which can be executed directly,
+then you can create a file in ".menu" format instead of the C code.
+
+NOTE: ".menu" files can only describe the very basic type of menus
+See MENU_FORMAT for the syntax of .menu files
The resulting code is a 32-bit COMBOOT code, and hence can be executed
only under syslinux. You can use tools like bochs to help debug your