| 88 | |
| 89 | == Starting Mars == |
| 90 | |
| 91 | On success, by starting root in your build directory, you should see a message like |
| 92 | {{{ |
| 93 | [0] root -l |
| 94 | |
| 95 | Loading 'libmars.so'... done. |
| 96 | |
| 97 | Welcome to the Mars Root environment. |
| 98 | |
| 99 | root [0] |
| 100 | }}} |
| 101 | |
| 102 | Be aware that it might be slightly different for different versions (in particular of root). |
| 103 | |
| 104 | You should not be able to use Mars. |
| 105 | |
| 106 | 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. |
| 107 | |
| 108 | |
| 109 | |