svn@coreboot.org wrote:
simplify source tree hierarchy: move files from sdram/ and ram/ to lib/ It's only three files. Also fix up all the paths (Gotta love included C files)
Definately a good change!
Do we have a strategy for the included C files? Will that be trivial once Kconfig has settled in?
//Peter
On Wed, Sep 23, 2009 at 1:51 PM, Peter Stuge peter@stuge.se wrote:
Do we have a strategy for the included C files? Will that be trivial once Kconfig has settled in?
it's going to be a bit longer than that. I've done complete seperate compilation for a few targets but, remember, if you're using romcc you're including .c files.
ron
ron minnich wrote:
Do we have a strategy for the included C files? Will that be trivial once Kconfig has settled in?
it's going to be a bit longer than that. I've done complete seperate compilation for a few targets but, remember, if you're using romcc you're including .c files.
Yes! Thanks! CAR is the key to that. But where there is CAR and Kconfig, maybe it could be fixed up fairly easily.
I hope we can support both CAR and romcc use of the same source without having to mess much with Kconfig.
//Peter
Peter Stuge wrote:
svn@coreboot.org wrote:
simplify source tree hierarchy: move files from sdram/ and ram/ to lib/ It's only three files. Also fix up all the paths (Gotta love included C files)
Definately a good change!
Do we have a strategy for the included C files? Will that be trivial once Kconfig has settled in?
Not more trivial than today, but there is a way out of the misery :-)
Having Kconfig completed will at least keep us from doing these changes in two different places. And they're an excellent excuse to drop the non-Kconfig build method.
I know people are eager to get rid of this, but one step after another, or the tree might fall apart..
Stefan
-
Peter Stuge -
ron minnich -
Stefan Reinauer