Dear Scott Wood, In message <[email protected]> you wrote: > > > Maybe they should use different variables then, say > > CONFIG_SYS_TEXT_BASE and CONFIG_SYS_TEXT_BASE_SPL ? > > Why? It's the same variable, just for a different build. Are we going > to have _SPL and non-_SPL variants of all other things that might vary > between the two?
This is a multistage process. Initially, we generate autoconf.mk by parsing the config files; then we include autoconf.mk in the Makefile to export the settings to make. If you change the value of one of the variables in a later stage of the build (like using #ifdef), then tis will not become visible in the Makefile context, i. e. any use of these variables for example in the Linker command will still use the old value. > What about a middle-stage build where we want to use CONFIG_ symbols to > pull in files like a regular U-Boot build, but we want to pull in a > different set than the final image? This is no problem as long as these variables doen't change their values on the fly. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] We are all agreed that your theory is crazy. The question which divides us is whether it is crazy enough to have a chance of being correct. My own feeling is that it is not crazy enough. - Niels Bohr _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
