Using imported target in CMake doesn't register signal handler about backward-cpp HOT 3 CLOSED

I added static_assert(false); to backward.cpp and it didn't fail compilation, which means this file is not used with the CMake configuration above. Is this intended behavior?

I found that the only advantage of this method is automatic detection of dependent libraries and setup of definitions, so later you can #include "external/backward.hpp" and create the SignalHandling object on the stack instead of a global scope.

from backward-cpp.

I'm closing this after coming to a conclusion that the original expected outcome was wrong. Backward-cpp does not create a global signal handler on its own, it is the user's responsibility to make it somewhere or add backward.cpp as a dependency of the executable.

from backward-cpp.

Yes, the backward.cpp file in the repo, is there as an example and starting point.

from backward-cpp.