We seem to have a productive dialog on how to organize main() and I am confident we will end up with something that works well. Therefore I feel the need to stir things up a bit. ;-) I also see a need to more versatile or cusom make rules. We have the standard rule for creating a romimage that is 64K "bios" and 448K of kernel image. This doesn't let me include initrd images or multiple kernel images for roms that are larger than 512K. Should NLBConfig.py grow to be able to include bits of custom Makefile rules? Is there an alternative that someone would like to suggest? This is really a top level config thing that applies more to the application the board is being used for than even the board itself. Though the capability isn't really missing, most of the discussion/origanization/tools don't seem to explicitly acknowledge an application level of configuration that is "above" the board level config. It currently exists as the top level config file that ends up including the board level config file so I'm really talking more about semantics/terminology than any significant missing capability. Cheers! Ty -- Tyson D Sawyer iRobot Corporation Senior Systems Engineer Real World Interface Div. [EMAIL PROTECTED] Robots for the Real World 603-532-6900 ext 206 http://www.irobot.com
