| | 13 | == CMake Build commands == |
| | 14 | |
| | 15 | CMake has several advantages over qmake or standard make files for multiplatform development. One advantage is that it lets one build out of source (which makes clean up if a build goes wrong much easer.) |
| | 16 | |
| | 17 | After installing cmake, change to the mussa source directory and do the following. |
| | 18 | |
| | 19 | {{{ |
| | 20 | mkdir build |
| | 21 | cd build |
| | 22 | cmake .. |
| | 23 | make |
| | 24 | cd qui |
| | 25 | ./mussagl |
| | 26 | }}} |
| | 27 | |
| | 28 | To run the unittests from with in the build directory type |
| | 29 | {{{ |
| | 30 | make test |
| | 31 | }}} |
| | 32 | or |
| | 33 | {{{ |
| | 34 | ctest |
| | 35 | }}} |
| | 36 | |
| | 37 | Some useful alternate modes for cmake are: |
| | 38 | {{{ |
| | 39 | make VERBOSE=1 |
| | 40 | }}} |
| | 41 | which will show the actual commands being used to compile the program, and |
| | 42 | {{{ |
| | 43 | cmake -VV |
| | 44 | }}} |
| | 45 | which will show the output of the various test programs. |
| | 46 | |
| | 47 | == QMake Build Command == |
| | 48 | |
| | 49 | Building with qmake (this can only build mussagl, it doesn't build the python interface or the unittests) |