Commit fbe57be9 authored by Dennis Gläser's avatar Dennis Gläser
Browse files

[cmake] remove add_aplication macro

This turns examples into "tests". We actually want to have them tested
in the ci as well. Moreover, the add_application macro was basically the
same as add_test, just not adding an actual test.
parent b737530e
frackit_add_application(NAME example1
SOURCES example1.cc
LABELS example)
frackit_add_test(NAME example1
SOURCES example1.cc
LABELS example)
frackit_symlink_or_copy(FILES example1.py)
......
frackit_add_application(NAME example2
SOURCES example2.cc
LABELS example)
frackit_add_test(NAME example2
SOURCES example2.cc
LABELS example)
frackit_symlink_or_copy(FILES example2.py)
......
frackit_add_application(NAME example3
SOURCES example3.cc
COMPILE_DEFINITIONS BREPFILE="layers.brep"
LABELS example)
frackit_add_test(NAME example3
SOURCES example3.cc
COMPILE_DEFINITIONS BREPFILE="layers.brep"
LABELS example)
frackit_symlink_or_copy(FILES example3.py layers.brep)
......
frackit_add_application(NAME example4
SOURCES example4.cc
LABELS example)
frackit_add_test(NAME example4
SOURCES example4.cc
LABELS example)
frackit_symlink_or_copy(FILES example4.py)
......
install(FILES
FrackitApplicationMacros.cmake
FrackitMacros.cmake
FrackitTestMacros.cmake
DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/cmake/modules)
# includes all relevant macros
include(FrackitTestMacros)
include(FrackitApplicationMacros)
include(FrackitCopyOrSymlink)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment