Split platform/application configuration file

[Nicolas Pouillon]

Configuration files contain both the platform definition and the libraries used by the application. Splitting them could allow reusing application definitions from different examples, and creating only one definition per application.

[Joël Porquet]

Do you think of specifying two files to the build system, or maybe adding an "include" directive in the configuration syntax, or something else?

[Joël Porquet]

Another idea could be merely to specify several config files when invocating the makefile: make CONF=conf_sys,conf_libs,conf_app In the internal buildsystem, we just have to 'cat' all those config file into one.

This way, one can have independent config files for each part of the kernel:

• config_arm_proc, config_mips_proc
• config_mono, config_smp2
• config_soclib
• config_migration, config_static
• config_elf, config_libtermui, config_lua
• etc

and build kernel in a very modular way: make CONF=config_mips_proc,config_smp2,config_soclib,etc

[Joël Porquet]

My bad, I should have look at the preview first...

Another idea could be merely to specify several config files when invocating the makefile:

make CONF=conf_sys,conf_libs,conf_app

In the internal buildsystem, we just have to cat all those config file into one.

This way, one can have independent config files for each part of the kernel:

• config_arm_proc, config_mips_proc
• config_mono, config_smp2
• config_soclib
• config_migration, config_static
• config_elf, config_libtermui, config_lua
• etc

and build kernel in a very modular way:

make CONF=config_mips_proc,config_smp2,config_soclib,etc

[Nicolas Pouillon]

I dont think we want to split them too deep, or we'll end up with configuration file contents on the command line :) and create shell scripts containing configuration command line :)

The build system already uses multiple configuration file for heterogeneous builds...

[Nicolas Pouillon]

Done as of [1120]