Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| gettinstarted [2020/09/09 16:31] – [Neptus] alberto | gettinstarted [2023/09/06 11:21] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 51: | Line 51: | ||
| ==== IMC ==== | ==== IMC ==== | ||
| < | < | ||
| - | cd aurlab | ||
| git clone https:// | git clone https:// | ||
| cd imc/ | cd imc/ | ||
| Line 58: | Line 57: | ||
| ==== Working with DUNE ==== | ==== Working with DUNE ==== | ||
| - | To start DUNE, you need to choose a configuration file (that is, a .ini-file). These files are placed under the // / | + | To start DUNE, you need to choose a configuration file (that is, a .ini-file). These files are placed under the // / |
| < | < | ||
| - | cd aurlab | + | ./dune -c ntnu-autonaut -p Simulation |
| - | cd dune | + | |
| - | git checkout -b the-branch-you-work-on | + | |
| - | </ | + | |
| - | Now you should have moved to your own branch. Every time you make something new on your branch, or do some major updates (minimum once a day), you should commit your changes. | + | |
| - | + | ||
| - | To run DUNE using your specific config file, you write | + | |
| - | + | ||
| - | < | + | |
| - | cd build | + | |
| - | cmake ../dune | + | |
| - | ./dune -c name.ini | + | |
| </ | </ | ||