Ok, so the current configs dir is a mess. I wanted to use it to try to create an example for my batch scripts, but as it is, the code is pretty messy, so I'd like to start a conversation about where we'd like to take the config stuff. I think the following are some goals:
1) Turn the configurations into a package 2) Move as much code as possible out of the various example files 3) Support the python -m command line option in M5. (and perhaps use the runpy module to do stuff in main.py) (Support -c as well?) 4) Move the examples stuff into the configs package and expect that -m will be used for examples (m5 -d -m configs.examples.se <options>) 5) get rid of addToPath usage Suggested steps: Move configs/common/* into configs/ Create empty configs/__init__.py Create empty configs/examples/__init__.py Move common/Options.py into configs/examples/Options.py Fix up imports. Should we rename configs to m5config? Comments? One question is, what do we do with the boot dir? I think we should just leave it. There's no prohibition against having data files in python packages. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
