> 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.
It's not documented because it was never fleshed out. The idea was that the python script was more like a config file. I looked at it again, and all it does is export the options dict. In general, I think that it would be a good idea for us to have a config file or config directory and support that. I just used a python script, for what I did and I think that works pretty well in general since it's less code for us to write. That said, if we were to make it useful, we would have to document it better. I could be convinced to have a .ini file for configuration stuff though. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
