1.) CMake build integration
-> Created CMakeLists.txt files for all the targets in src/ and misc/
-> "standard CMake building" may take place due to this
2.) CMake Module installation
-> building with CMake and then installing locally (edit CMAKE_INSTALL_PREFIX !) results in a CMake Module "XA65" being installed, which can be found thru "find_package( XA65 )" in other CMake-based projects.
-> uses the CMake-code in added subdir "cmake"
3.) CPack packaging - only tested on Windows using NSIS installer system
-> creates a distributable installer "xa65--.exe"
-> after installing, users can "find_package( XA65 )" in their projects with more ease, as - on Windows - XA65 gets installed into $ENV(ProgamFiles)
1.) CMake build integration -> Created CMakeLists.txt files for all the targets in src/ and misc/ -> "standard CMake building" may take place due to this 2.) CMake Module installation -> building with CMake and then installing locally (edit CMAKE_INSTALL_PREFIX !) results in a CMake Module "XA65" being installed, which can be found thru "find_package( XA65 )" in other CMake-based projects. -> uses the CMake-code in added subdir "cmake" 3.) CPack packaging - only tested on Windows using NSIS installer system -> creates a distributable installer "xa65--.exe"
-> after installing, users can "find_package( XA65 )" in their projects with more ease, as - on Windows - XA65 gets installed into $ENV(ProgamFiles)