created advanced CMake integration#22
Open
St0fF-NPL-ToM wants to merge 5 commits into
Open
Conversation
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-<version>-<arch>.exe" -> after installing, users can "find_package( XA65 )" in their projects with more ease, as - on Windows - XA65 gets installed into $ENV(ProgamFiles)
just a copy of how it is done in file65.c
- corrected build type preselection - added option to select, how many bytes per line shall be printed in hex-mode - in-source documentation updated
... due to testing results
- "modern CMake" needs no package configuration file being configured. It simply needs to include the exports-file. -> thus XA65Config.in.cmake was removed, it's neccessary content put into former XA65Functions.cmake, which was renamed to XA65Config.cmake to be the new package config file including our functionality. - also added the latest win64-installer to the repo for convenience/testing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)