Framework providing operating system abstractions and a range of shared networking (RDMA, TCP/IP) and memory services to common modern heterogeneous platforms.
The instructions to build software in the Coyote documentation don't work for out-of-tree builds because FindCoyoteSW.cmake uses CMAKE_SOURCE_DIR to identify sources and this envvar is set to the location of the caller CMakeLists.txt. In the case of Coyote software examples in examples_sw it just happens that the relative paths overlap.
You can confirm that this is the case as follows:
move examples_sw to a new directory e.g. Coyote/foo/examples_sw and cd into it
edit line 4 of Coyote/foo/examples_sw/CMakeLists.txt to point to the Coyote top-level folder
run cmake -DEXAMPLES=reconfigure_shell .
The output of this will be
CMake Error at Coyote/cmake/FindCoyoteSW.cmake:93 (add_library):
No SOURCES given to target: Coyote
Call Stack (most recent call first):
CMakeLists.txt:7 (find_package)
This can be fixed by using CMAKE_CURRENT_LIST_DIR instead of CMAKE_SOURCE_DIR in FindCoyoteSW.cmake
The instructions to build software in the Coyote documentation don't work for out-of-tree builds because FindCoyoteSW.cmake uses
CMAKE_SOURCE_DIRto identify sources and this envvar is set to the location of the callerCMakeLists.txt. In the case of Coyote software examples inexamples_swit just happens that the relative paths overlap.You can confirm that this is the case as follows:
examples_swto a new directory e.g.Coyote/foo/examples_swand cd into itCoyote/foo/examples_sw/CMakeLists.txtto point to the Coyote top-level foldercmake -DEXAMPLES=reconfigure_shell .The output of this will be
This can be fixed by using
CMAKE_CURRENT_LIST_DIRinstead ofCMAKE_SOURCE_DIRinFindCoyoteSW.cmake