config.py moved?
Stefan Reinauer
stepan at suse.de
Mon Oct 13 14:48:01 CEST 2003
* ron minnich <rminnich at lanl.gov> [031013 20:47]:
> On Mon, 13 Oct 2003, Stefan Reinauer wrote:
>
> > This is probably a henn-egg-problem - the target directory is created
> > by config.py, isn't it?
>
> for
> targets/arima/hdama
>
> you could put config.py in targets/arima/hdama, while the build is done in
> targets/arima/hdama/hdama
Is this safe when you have for example tarets/arima/hdama/hdama-8mbit
and targets/arima/hdama/hdama-4mbit built on different systems? This
might already be philosophic though.
I generally don't like in-tree builds either. But the boundaries are
fuzzy, it is also of interest to keep the config files close to the
builds they belong to. Otherwise I would suggest moving Config.lbs from
targets/ to mainboards/ as Buildconfig.lb or Config.Bld and have the
targets directory flat for built stuff only.
Stefan
--
Architecture Team
SuSE Linux AG
More information about the coreboot
mailing list