Styjun

Who was this character from the Tomb of Annihilation adventure before they became a monster?

What to do if SUS scores contradict qualitative feedback?

Does kinetic energy warp spacetime?

How are one-time password generators like Google Authenticator different from having two passwords?

How do I tell my supervisor that he is choosing poor replacements for me while I am on maternity leave?

Find the cipher used

What's the word for the soldier salute?

Run script for 10 times until meets the condition, but break the loop if it meets the condition during iteration

Is there a spell to protect inanimate objects?

What does i386 mean on macOS Mojave?

Can I make ravioli dough with only all-purpose flour or do I NEED semolina flour?

Understanding integration over Orthogonal Group

Size of a folder with du

Can the sorting of a list be verified without comparing neighbors?

As programers say: Strive to be lazy

Setting the major mode of a new buffer interactively

Meaning of「〜てみたいと思います」

Does Lawful Interception of 4G / the proposed 5G provide a back door for hackers as well?

Extracting sublists that contain similar elements

iMac 27" 2017 memory upgrade question

Why was castling bad for white in this game, and engine strongly prefered trading queens?

"Right on the tip of my tongue" meaning?

Why was Thor doubtful about his worthiness to Mjolnir?

How can this triangle figure be modeled/drawn with TikZ?

CMake Tests for a library intended as a git submodule

CMake exclude tests in subdirectoriesHow do I discard unstaged changes in Git?How to remove local (untracked) files from the current Git working tree?What is the difference between 'git pull' and 'git fetch'?How to undo 'git add' before commit?How do I undo the most recent local commits in Git?How do I force “git pull” to overwrite local files?How do I check out a remote Git branch?How do I delete a Git branch locally and remotely?How to revert a Git repository to a previous commitHow do I rename a local Git branch?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

Situation: You develop a library which uses CMake as its (meta-)buildsystem. The library is header-only (actually it does need to, the question still applies), has tests and examples (like benchmarks). The library can be used by installing it and using the resulting package files or (which is often easier to avoid mismatches in ABIs) by adding it as a git submodule and simply add_subdirectory it.

Question: What is the best way to handle tests in that library?

Usually the top-level CMake will look like this:

[...setup code, project(...)`]
add_library(foo src/foo.cpp)
target_include_libraries(foo PUBLIC include)

include(CTest)
if(BUILD_TESTING)
 add_subdirectory(tests)
endif()
if(FOO_BUILD_EXAMPLES)
 add_subdirectory(examples)
endif()
install(TARGETS foo ...)
install(...)

The issue I have with this is that when this is used as a submodule and the super project also uses include(CTest) and BUILD_TESTING then enabling the super projects tests enables also the submodule tests.

Is this what should be done and expected?

Similar for the install commands: Installing the super project installs also the submodule (I think) which may be wrong as the CMAKE_INSTALL_PREFIX given was intended for the super project and might not be appropriate for the submodule.

This would lead to using prefixes and options like FOO_BUILD_TESTING and FOO_INSTALL but I don't see them used often.

Am I worrying to much or missing anything? What is the way to go with building (and running) tests and installs for git submodules?

git testing cmake

share|improve this question

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  "This would lead to using prefixes and options like FOO_BUILD_TESTING and FOO_INSTALL but I don't see them used often." - This is not so rare as you think. E.g. libevent uses EVENT__DISABLE_TESTS for disable tests, see that question: stackoverflow.com/questions/23713650/…. Actually, the problem is not specific for testing, this is common for all projects which allow to be "embedded" into other projects, and want to be tunable.
  
  – Tsyvarev
  Mar 23 at 12:53
  

  
  
  
  

add a comment | 

1

Situation: You develop a library which uses CMake as its (meta-)buildsystem. The library is header-only (actually it does need to, the question still applies), has tests and examples (like benchmarks). The library can be used by installing it and using the resulting package files or (which is often easier to avoid mismatches in ABIs) by adding it as a git submodule and simply add_subdirectory it.

Question: What is the best way to handle tests in that library?

Usually the top-level CMake will look like this:

[...setup code, project(...)`]
add_library(foo src/foo.cpp)
target_include_libraries(foo PUBLIC include)

include(CTest)
if(BUILD_TESTING)
 add_subdirectory(tests)
endif()
if(FOO_BUILD_EXAMPLES)
 add_subdirectory(examples)
endif()
install(TARGETS foo ...)
install(...)

The issue I have with this is that when this is used as a submodule and the super project also uses include(CTest) and BUILD_TESTING then enabling the super projects tests enables also the submodule tests.

Is this what should be done and expected?

Similar for the install commands: Installing the super project installs also the submodule (I think) which may be wrong as the CMAKE_INSTALL_PREFIX given was intended for the super project and might not be appropriate for the submodule.

This would lead to using prefixes and options like FOO_BUILD_TESTING and FOO_INSTALL but I don't see them used often.

Am I worrying to much or missing anything? What is the way to go with building (and running) tests and installs for git submodules?

git testing cmake

share|improve this question

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  "This would lead to using prefixes and options like FOO_BUILD_TESTING and FOO_INSTALL but I don't see them used often." - This is not so rare as you think. E.g. libevent uses EVENT__DISABLE_TESTS for disable tests, see that question: stackoverflow.com/questions/23713650/…. Actually, the problem is not specific for testing, this is common for all projects which allow to be "embedded" into other projects, and want to be tunable.
  
  – Tsyvarev
  Mar 23 at 12:53
  

  
  
  
  

add a comment | 

Situation: You develop a library which uses CMake as its (meta-)buildsystem. The library is header-only (actually it does need to, the question still applies), has tests and examples (like benchmarks). The library can be used by installing it and using the resulting package files or (which is often easier to avoid mismatches in ABIs) by adding it as a git submodule and simply add_subdirectory it.

Question: What is the best way to handle tests in that library?

Usually the top-level CMake will look like this:

[...setup code, project(...)`]
add_library(foo src/foo.cpp)
target_include_libraries(foo PUBLIC include)

include(CTest)
if(BUILD_TESTING)
 add_subdirectory(tests)
endif()
if(FOO_BUILD_EXAMPLES)
 add_subdirectory(examples)
endif()
install(TARGETS foo ...)
install(...)

The issue I have with this is that when this is used as a submodule and the super project also uses include(CTest) and BUILD_TESTING then enabling the super projects tests enables also the submodule tests.

Is this what should be done and expected?

Similar for the install commands: Installing the super project installs also the submodule (I think) which may be wrong as the CMAKE_INSTALL_PREFIX given was intended for the super project and might not be appropriate for the submodule.

This would lead to using prefixes and options like FOO_BUILD_TESTING and FOO_INSTALL but I don't see them used often.

Am I worrying to much or missing anything? What is the way to go with building (and running) tests and installs for git submodules?

git testing cmake

share|improve this question

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127

[...setup code, project(...)`]
add_library(foo src/foo.cpp)
target_include_libraries(foo PUBLIC include)

include(CTest)
if(BUILD_TESTING)
 add_subdirectory(tests)
endif()
if(FOO_BUILD_EXAMPLES)
 add_subdirectory(examples)
endif()
install(TARGETS foo ...)
install(...)

share|improve this question

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127

share|improve this question

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127

asked Mar 23 at 11:58

FlamefireFlamefire

1,4971127