| 52 | | Our build toolchain uses the ''cmake'' framework. For all build processes we recommend an ''out-of-source'' build, this complies to ''cmake BCP''. |
| | 52 | Our build toolchain uses the ''cmake'' framework. For all build processes we recommend an ''out-of-source'' build, this complies to ''cmake BCP''. Our ''core'' release contains a ''main'' CMakeLists.txt, that recursivly builds libhamcast, middleware and modules. To build the full core release, follow these steps: |
| | 53 | |
| | 54 | * change to core release folder {{{hamcast_core/}}} |
| | 55 | * create a build folder, e.g. {{{hamcast_core/build}}} |
| | 56 | * change to build folder |
| | 57 | * run cmake: |
| | 58 | {{{ |
| | 59 | cmake ../ |
| | 60 | }}} |
| | 61 | * If no errors occure cmake creates a Makefile, run in build folder: |
| | 62 | {{{ |
| | 63 | make |
| | 64 | }}} |
| | 65 | * Afterwards all libraries (libhamcast and modules) are stored in {{{hamcast_core/lib}}} and the middleware in {{{hamcast_core/bin}}} |
| | 66 | |
| | 67 | You can also compile each part of HAMcast separately, see instructions below. |
