Edward Diener

The comment in backward.hpp says that only one of the symbols should be set at a time. So it does not seem that libdw and libdwarf (and libelf) can be...

> Yes, and you can use bcm_test_link_libraries for that, which is just links a library but you can use an interface library to build a library that is just a...

> A bcm_test is both a cmake test and a target(which can be either an executable or library). The target will link against any libraries that were specified in the...

I apologize getting so heated up over a general argument over whether the library developer should be able to set the C++ standard level of compliance for particular tests. The...

Looking at CMake it appears there are properties that can be set on source files using set_source_file_properties. Among these source file properties which can be set are COMPILE_DEFINITIONS and COMPILE_FLAGS....

That is my misunderstanding then. I thought you could use set_source_file_properties to add the properties to the CMakeLists.txt file itself so that all builds referenced in the CMakeLists.txt file had...

Are you saying that setting directory properties do not set the appropriate properties when creating targets from the files in that directory ( and sub-directories ) ? If that is...

If I therefore set a directory property in a CMakeLists.txt file for tests, that property will filter down to all test targets which are built in that CMakeLists.txt file. This...

I have also seen this occur occassionally in the 'develop' branch of Build when I try to invoke an invalid toolset, for which I have no 'using...' definition, or a...

This should be: using msvc : 14.0 ;