I’ve been helping a friend improve it’s SDR (Software Defined Radio) project by trying to improve the build system.
The project has gotten to a point where everything seems to be quite stable and functional so I wanted to start hacking on a unit testing infrastructure. My tech stack is CMake + CTest + Catch2.
The project structure is as follows:
src- source code of the sigutils library.
tests- source code that generates the test binaries.
The source code can be found at GitHub - antoniovazquezblanco/sigutils at dev/tests.
Currently, the base
CMakeLists.txt adds the
src dir. In the
src/CMakeLists.txt the sigutils library target is defined and everything seems to be working as expected. In linux, this target generates an
.so file, a
.dll in windows and a
.dylib in MacOS…
At the bottom, the base
CMakeLists.txt adds the
tests dir and attempts to generate an executable for CTest to execute later on…
I am having problems compiling and executing the tests:
- On linux things seem to be working…
- On MacOS things break during the compilation phase due to a
dyld: Library not loaded: '@rpath/libsigutils.1.dylib' Referenced from: '/Users/runner/work/sigutils/sigutils/build/tests/sigutils_test' Reason: tried: '/usr/local/lib/libsigutils.1.dylib' (no such file), '/usr/lib/libsigutils.1.dylib' (no such file)
- On Windows things break when calling CTest with an exception while executing the tests due to being unable to load our library when executing the test;
1/1 Test #1: Test normalized frecuency scale ...Exit code 0xc0000135
Build and test logs:
- Linux Add a sample testing structure · antoniovazquezblanco/sigutils@7b1feb2 · GitHub
- MacOS Add a sample testing structure · antoniovazquezblanco/sigutils@7b1feb2 · GitHub
- Windows Add a sample testing structure · antoniovazquezblanco/sigutils@7b1feb2 · GitHub
I am currently linking the library with the following command:
I am also trying to execute the tests in the
src working directory to be able to find the lib:
catch_discover_tests(sigutils_test WORKING_DIRECTORY "$<TARGET_FILE_DIR:sigutils>")
I don’t know if I am making things difficult for myself or if my approach is generally oriented with good CMake practices. Any orientation in this regard is appreciated… Some of the doubts I had during the process include:
- Should I compile a static version of the lib and always statically link the tests? This may take longer but it ensures everything works…
- I would rather not mix library code and test code but, is there any alternative?
- Should the library be copied to the tests folder on library compilation? Seems a weird approach…
Thanks in advance!