[syslinux] vesamenu.c32 + include + CLI woes

[Bryan Perry]

It is ugly, but there is a way to do it (I have plans for a much cleaner 
implementation, but I'm being way too busy unfortunately.)

This is how: have your main configuration file contain:

-------------
# This is where we start the menu tree...
default vesamenu.c32 main.cfg

include main.cfg
include submenu1.cfg
include submenu2.cfg
include submenu3.cfg
--------------

The trick is that the root of the menu tree doesn't actually have to be 
your main configuration file (the one that's read by the CLI.)  Thus, 
you can have the main configuration file include ALL your submenus, and 
therefore seeing all the labels (at least up to the 64K limit in the CLI.)

	-hpa


Right, I have played with that option too. The problem I have is that all of the label statements from the included submenu config files still show up in the main menu where I only want menu options to go to the submenus. In looking through the documentation I am lead to believe that the INCLUDE directive should not put the labels in the menu, only the MENU INCLUDE directive should do that but it doesn't appear to be working that way.

If the INCLUDE directive only included the configuration and did not alter the main menu this would be the perfect way to solve my problem.

By the way, thanks for the response. It's surprising how many open source projects don't get any response from developers.

-Bryan