config.py moved?

Eric W. Biederman ebiederman at lnxi.com
Mon Oct 13 11:31:00 CEST 2003


Stefan Reinauer <stepan at suse.de> writes:

> * ron minnich <rminnich at lanl.gov> [031013 17:07]:
> > > config.py moved to the target directory. Did this happen on purpose?
> > > Should it not move to config/solo/solo instead of config/solo if it
> > > moves at all?
> > 
> > config.py shouldn't even be in cvs. It is derived from config.g. 
> 
> Yes, that's why util/newconfig has the following entries in it's
> .cvsignore:
> config.py
> yappsrt.pyc
> parsedesc.py
> 
> > I think you are right, however, for a given target there probably ought to 
> > be a config.py for that target, since not all targets are built on the 
> > same box. 
> 
> This is probably a henn-egg-problem - the target directory is created
> by config.py, isn't it?

Yes.  And that is why I only almost moved it where it is supposed to
go.

We also have a bunch of dependency problems with the new config
system as well.

But at least the mechanism for how to move it is now implemented
so we can finish the last of those pieces.

For those who have not seen exactly what we are talking about
look at the latest changes to buildtarget.

Eric



More information about the coreboot mailing list