init: don't build files that centralize python and swig code
authorNathan Binkert <nate@binkert.org>
Thu, 9 Sep 2010 21:15:42 +0000 (14:15 -0700)
committerNathan Binkert <nate@binkert.org>
Thu, 9 Sep 2010 21:15:42 +0000 (14:15 -0700)
commite6ee56c6571999631ce31b05d0e563d66a7bbdd8
tree174a7431f8a5b5e80c90b8a9887c90b245af07d8
parent710ed8f492aa783933df6551ff98c9a6750fd9f7
init: don't build files that centralize python and swig code

Instead of putting all object files into m5/object/__init__.py, interrogate
the importer to find out what should be imported.
Instead of creating a single file that lists all of the embedded python
modules, use static object construction to put those objects onto a list.
Do something similar for embedded swig (C++) code.
src/SConscript
src/python/SConscript
src/python/m5/objects/__init__.py [new file with mode: 0644]
src/sim/init.cc
src/sim/init.hh