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.
This commit is contained in:
@@ -49,6 +49,7 @@ PySource('m5', 'm5/simulate.py')
|
||||
PySource('m5', 'm5/stats.py')
|
||||
PySource('m5', 'm5/ticks.py')
|
||||
PySource('m5', 'm5/trace.py')
|
||||
PySource('m5.objects', 'm5/objects/__init__.py')
|
||||
PySource('m5.util', 'm5/util/__init__.py')
|
||||
PySource('m5.util', 'm5/util/attrdict.py')
|
||||
PySource('m5.util', 'm5/util/code_formatter.py')
|
||||
|
||||
Reference in New Issue
Block a user