# Changes between Version 9 and Version 10 of InstallingMars

Ignore:
Timestamp:
Nov 7, 2018, 4:03:15 PM (10 months ago)
Comment:

--

### Legend:

Unmodified
 v9 == Compiling FACT++ == == Compiling Mars == Then call where '''N''' is the numbers of threads you want to utilize (check the number of CPU cores you can keep busy). Or you can omit the {{{-jN}}} in case you want to run on a single CPU. == Starting Mars == On success, by starting root in your build directory, you should see a message like {{{ [0] root -l Loading 'libmars.so'... done. Welcome to the Mars Root environment. root [0] }}} Be aware that it might be slightly different for different versions (in particular of root). You should not be able to use Mars. How does that work? When you start root in your build directory, it reads .rootrc in your build directory. This file points to rootlogon.C in your build directory. This macro is executed when on root startup and loads the shared object lib/libmars.so. As all this uses absoluet paths, you could even move .rootrc into your home directory and get the Mars environment no matter where you start root. As this works only with absolute paths, you might not change or rename the build directory without changing those files. == Known to work ==