1) The user has ndiff available for testing without manual intervention
2) The tests run by ctest use the version of ndiff found or installed by cmake
3) The warm snake data is cached to the source tree and the build tree so that you don't need to download it whenever the build tree is removed
This should ensure that:
If you have ndiff installed on your system, CMake should pick it up, assuming it's on your PATH and in a standard location like /usr/local/bin or similar
If you do not have ndiff installed, a stripped down version of the contents of the source archive are now included in vendor/ndiff-2.00
If you do not have ndiff pre-installed CMake will build the vendored version as part of the build process so that it is available for testing with ctest
To manually build ndiff (and nothing else) ensure that you don't already have ndiff installed and then:
Configure the project normally:
mkdir build
cd build
cmake ..
Then, make ndiff
This does an "in source" build of ndiff, so it will write files to your source tree
make clean in vendor/ndiff-2.00 will get some of the build artifacts but...
running git clean -f -d -x or git clean -i -d -x (the latter is interactive and therefore safer) will remove other ndiff build artifacts
Leaving ndiff build artifacts in your source tree should not be an issue unless you are cross-mounting the source directory on a linux VM and also building natively under, e.g., macOS.
This PR ensures that:
1) The user has
ndiffavailable for testing without manual intervention 2) The tests run by ctest use the version of ndiff found or installed by cmake 3) The warm snake data is cached to the source tree and the build tree so that you don't need to download it whenever the build tree is removedThis should ensure that:
/usr/local/binor similarvendor/ndiff-2.00mkdir buildcd buildcmake ..make ndiffmake cleaninvendor/ndiff-2.00will get some of the build artifacts but...git clean -f -d -xorgit clean -i -d -x(the latter is interactive and therefore safer) will remove other ndiff build artifactsLeaving ndiff build artifacts in your source tree should not be an issue unless you are cross-mounting the source directory on a linux VM and also building natively under, e.g., macOS.