On 2/9/10 9:06 AM, Peter Stuge wrote:
What happens in the build: kconfig generates config.h, which carries all the CONFIG_* definitions. The build.h file is created by make rules and contains a couple more definitions, mostly those with COREBOOT_*, and an include of config.h.
Aha. Could we get COREBOOT_* into config.h somehow?
Why?
Maybe add functionality to Kconfig so that it adds all environment variables with a certain prefix to config.h?
Sounds hackish; the config would have to be rewritten for every compile. build.h contains build specific information, config.h contains configuration. That was the reason we created two files of them to begin with... In v2 it was only one file.
What about this:
We -include config.h and have dependencies on build.h only where needed. In theory this could be two object files. In practice it's a few more because we include the C file in every romstage.c.
Stefan