On 02/21/11 18:37, nathan binkert wrote: >> I seem to remember being able to change things like SysPaths in it, or at >> least how Nate intended it to work. Of course, there's no documentation >> about it and the code is confusing, so i dunno... >> Let me ponder the other stuff in this for a day or two... > What's confusing? I added it mostly for me, but we can of course > document it. options.py is just executed before main() is executed > and it's done within the context of m5.main. You can in theory do > anything you want in there, though the intent was to override default > option values there. We could do something similar in SysPaths (exec > .m5/paths.py) to set the default SysPaths. > > Nate > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev
I don't know if we should expect people to reach into main.py like that in a per user way. It does the job setting default values, but does anybody use that even? Nobody seems to have known it existed. I think setting an environment variable is a lot more straightforward than writing a python script that fiddles with M5's innards. Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
