On Tue, 9 Nov 2010 18:18:53 +0100 Wolfgang Denk <w...@denx.de> wrote:
> Dear Scott Wood, > > In message <20101109102643.45d7f...@udp111988uds.am.freescale.net> 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. It's not "on the fly", it's just that each image needs its own autoconf.mk. -Scott _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot