Hi,
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?
Stefan
Stefan Reinauer stepan@suse.de writes:
Hi,
config.py moved to the target directory. Did this happen on purpose?
Yes, we should not have any generated files in the source directory.
Should it not move to config/solo/solo instead of config/solo if it moves at all?
Yes. I could not see a good way to move it there so I at least showed what it takes to move config.py.
Eric
On Mon, 13 Oct 2003, Stefan Reinauer wrote:
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.
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.
ron
* ron minnich rminnich@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?
Best regards, Stefan Reinauer
Stefan Reinauer stepan@suse.de writes:
- ron minnich rminnich@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
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
ron
ron minnich rminnich@lanl.gov writes:
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
That is exactly what buildtarget does now.
Eric
* Eric W. Biederman ebiederman@lnxi.com [031013 21:13]:
ron minnich rminnich@lanl.gov writes:
you could put config.py in targets/arima/hdama, while the build is done in targets/arima/hdama/hdama
That is exactly what buildtarget does now.
Is the config.py different from machine to machine? If not, I suggest we leave it like this. Otherwise I would have to come up with some solution, since I use multiple config files in targets/ now to easily build on different machines (opteron images on ia32 and amd64)
Stefan
Stefan Reinauer stepan@suse.de writes:
- Eric W. Biederman ebiederman@lnxi.com [031013 21:13]:
ron minnich rminnich@lanl.gov writes:
you could put config.py in targets/arima/hdama, while the build is done in targets/arima/hdama/hdama
That is exactly what buildtarget does now.
Is the config.py different from machine to machine? If not, I suggest we leave it like this. Otherwise I would have to come up with some solution, since I use multiple config files in targets/ now to easily build on different machines (opteron images on ia32 and amd64)
config.py should not change, but if we edit config.g we cannot create a proper dependency for config.py
I have just updated buildtarget so that it looks at Config.lb to see what the target directory is removing the chicken and the egg problem.
Now buildtarget just needs a final tweak so I can specify an out of tree build directory. Everything can now be deleted with one rm -rf and we can setup the dependencies in the makefile to rebuild config.py when config.g changes.
Eric
On Mon, 13 Oct 2003, Stefan Reinauer wrote:
Is the config.py different from machine to machine? If not, I suggest we leave it like this. Otherwise I would have to come up with some solution, since I use multiple config files in targets/ now to easily build on different machines (opteron images on ia32 and amd64)
It should not differ from machine to machine, but Python is always ready to surprise me. I vote we leave it where it is.
ron
Stefan,
I just tried to reproduce the problem and it worked fine here on both a 32bit and a 64bit compile. I have some size issues so it did not build a working image but I don't see a segfault.
Eric
* ron minnich rminnich@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
On Mon, 13 Oct 2003, Stefan Reinauer wrote:
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.
Hmm, I guess it is not but I figured that boards of "a type" would be built on the same system.
ron
-
ebiederman＠lnxi.com -
ron minnich -
Ronald G. Minnich
-
Stefan Reinauer