2.7 project-setup Model Builder functionality

SYNOPSIS

project-setup [options] [project]

DESCRIPTION

This section only includes the Model Builder specific functionality of project-setup. The documentation for the basic functionality can be found in the Simics Reference Manual.

OPTIONS

--device=DEVICE_NAME, --dml-device=DEVICE_NAME Generate skeleton code for a device, suitable to use as a starting point for implementing your own device. The default implementation language is DML. See the –c-device and –py-device options for creating devices using other languages. If the device already exists, this option is ignored. To recreate the skeleton, remove the device directory.
--c-device=DEVICE_NAME Similar to –device, but creates a device using C instead of DML.
--c++-device=DEVICE_NAME Similar to –device, but creates a device using C++ instead of DML.
--py-device=DEVICE_NAME Similar to –device, but creates a device using Python and the pyobj module instead of DML.
--py-device-confclass=DEVICE_NAME Similar to –device, but creates a device using Python and the confclass module instead of DML.
--component=COMPONENT_NAME Similar to –device, but creates a component skeleton in Python.
--copy-module=MODULE_NAME Copies the source code of a module into the project. The files will be copied from a matching module in one of the associated add-on packages. If the module does not exist in any add-on package, all possible modules are listed. If the module already exist in the project, it must be manually deleted first.
--copy-test=TEST_SUITE Copies the test suite into the project. The suite will be copied from Simics Base or one of the associated add-on packages. If the module does not exist in any add-on package, all possible modules are listed. If the test suite already exist in the project, it must be manually deleted first.
--list-modules List the modules with source code that can be copied into the project using the –copy-module argument.
--osa-tracker=TRACKER_NAME Generate skeleton code for an OS Awareness tracker, suitable to use as a starting point for implementing your own OS Awareness tracker. If the module already exists, this option is ignored. To recreate the skeleton, remove the module directory. The skeleton will be created in a directory named after the TRACKER_NAME and suffixed with ‘-tracker’.
--instrumentation-tool=TOOL_NAME Generate skeleton code for an instrumentation tool, suitable to use as a starting point for implementing your own tool. If the module already exists, this option is ignored. To recreate the skeleton, remove the module directory. The skeleton will be created in a directory named after the TOOL_NAME.
--instrumentation-filter=FILTER_NAME Generate skeleton code for an instrumentation filter, suitable to use as a starting point for implementing your own filter. If the module already exists, this option is ignored. To recreate the skeleton, remove the module directory. The skeleton will be created in a directory named after the FILTER_NAME.