Don't use GLIBCXX_ASSERTIONS in production
2 unresolved threads
2 unresolved threads
Compare changes
- kraus authored
+ 10
− 1
@@ -26,6 +26,13 @@ set (CMAKE_CXX_FLAGS_RELWITHDEBINFO "-O3 -g ")
@@ -101,7 +108,9 @@ elseif (${CMAKE_CXX_COMPILER_ID} MATCHES "GNU")
@kraus sorry, did not saw this MR.
Actually I would prefer to have this option in for all build types as long as the code has not been released. Hence in the master it should be in for all build types.
Ok, that's fine for me. However we then should extend the description of the procedure to release new versions such that you (or who ever prepares a new release) don't forget to remove this flag.
We can use the version number or another mechanism for this.
Could you make a more discreet proposition? E.g. always off when minor version is even?
I see these two options:
CMakeLists.txt
. This has the advantage of being more independent from the version numbers - just in case we want to change the numbering scheme.Ok, I've opted for the second proposition.