[
https://issues.apache.org/jira/browse/DISPATCH-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274447#comment-17274447
]
ASF GitHub Bot commented on DISPATCH-1929:
------------------------------------------
jiridanek opened a new pull request #1005:
URL: https://github.com/apache/qpid-dispatch/pull/1005
This is the way LLVM configures this. It allows turning on asserts
irrespective of the chosen CMAKE_BUILD_TYPE.
I read through
https://stackoverflow.com/questions/22140520/how-to-enable-assert-in-cmake-release-mode/65954915
and this seemed the most straight-forward solution. I'd like to turn this on
in some/most (and maybe all-except-one) CI builds.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Allow producing a release build with asserts enabled
> ----------------------------------------------------
>
> Key: DISPATCH-1929
> URL: https://issues.apache.org/jira/browse/DISPATCH-1929
> Project: Qpid Dispatch
> Issue Type: New Feature
> Affects Versions: 1.14.0
> Reporter: Jiri Daněk
> Priority: Major
> Fix For: 1.16.0
>
>
> The Clang compiler has a CMake option which enables asserts in C code in any
> build type, including ReleaseWithDebugInfo, etc. This seems like an useful
> thing to have.
> Coverity warns about assert calls with side effects, so enabling asserts all
> the time should be safe (Coverity would scream if it had any effects on
> functionality).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
