Hi,
I'm using CMake to generate makefiles to build my C++ projects with g++. When
developing code I find it useful to post-process g++ output. In particular I
like to feed the output through gSTLFilt.pl [0] and a custom version of colorgcc
[1].
Currently I have a wrapper around make (I call
Hi,
I was wondering if there was a way to access a list of all tests that were added
using add_test. Ideal would be to access the binary names and full path of the
tests, like a variable that contains all of them or something.
Thanks in advance,
seb
Hi,
James Amundson amundson@... writes:
Are there any CMake solutions for running tests in a cross-compiling
environment? Right now I have a lovely test suite that runs over sixty
different executables using the standard CMake and CTest setup. It works
exactly as I want under Linux, but now
Bill Hoffman bill.hoff...@... writes:
No need for all the complication...
If you already know where the library is going to be:
${CMAKE_CURRENT_BINARY_DIR}/kernels/libkernel_executable.a
Then link directly to the full path:
target_link_libraries(main_target
Michael Hertling mhertl...@... writes:
1) In the top-level CMakeLists.txt, you might say
SET_SOURCE_FILES_PROPERTIES(
main.cpp PROPERTIES OBJECT_DEPENDS
${CMAKE_CURRENT_BINARY_DIR}/kernels/libkernel_executable.a
)
When libkernel_executable.a has changed, this results in
Hi,
I have a somewhat weird setup to build binaries for the Cell processor:
|-- CMakeLists.txt
|-- kernels
| |-- CMakeLists.txt
| `-- kernel.cpp
`-- main.cpp
From the main.cpp in the root directory the executable is built.
In the kernels folder strange things (have to) happen: first the
