Setting up your development environment
This is going to talk about getting started developing gem5.
When modifying any open source project, it is important to follow the project’s style guidelines. Details on gem5 style can be found on the gem5 Coding Style page.
To help you conform to the style guidelines, gem5 includes a script
which runs whenever you commit a changeset in git. This script should be
automatically added to your .git/config file by SCons the first time you
build gem5. Please do not ignore these warnings/errors. However, in the
rare case where you are trying to commit a file that doesn’t conform to
the gem5 style guidelines (e.g., something from outside the gem5 source
tree) you can use the git option
--no-verify to skip running the style
The key takeaways from the style guide are:
- Use 4 spaces, not tabs
- Sort the includes
- Use capitalized camel case for class names, camel case for member variables and functions, and snake case for local variables.
- Document your code
Most people developing with gem5 use the branch feature of git to track their changes. This makes it quite simple to commit your changes back to gem5. Additionally, using branches can make it easier to update gem5 with new changes that other people make while keeping your own changes separate. The Git book has a great chapter describing the details of how to use branches.