Automatic builds without NDEBUG? - matplotlib-devel - Matplotlib
Automatic builds without NDEBUG? Development matplotlib-devel _Jouni_K_Seppanen April 19, 2014, 2:53pm 1 I was prompted by https://github.com/matplotlib/matplotlib/issues/2916 to run some static checkers on the C/C++ extension modules, and I was going to submit some simple fixes as pull requests, including assertions of some preconditions. I just realized that our build system sets the -DNDEBUG compiler flag, which makes sense for release builds but could hide problems in test builds.
Do any of our Travis, Launchpad, or other daily builds undefine NDEBUG? ··· -- Jouni K. Sepp�nen http://www.iki.fi/jks Thomas_Kluyver April 19, 2014, 6:56pm 2 I don't think the Launchpad builds undefine that, unless Launchpad does it for all builds by default. Thomas ··· On 19 April 2014 07:53, Jouni K. Seppänen < [email protected] ...> wrote: Do any of our Travis, Launchpad, or other daily builds undefine NDEBUG?
Michael_Droettboom April 21, 2014, 5:36pm 3 I think this is brought in from the parameters that were used to build Python itself. (The matplotlib build system doesn't explicitly add it). If you build matplotlib with a debug Python, you get a debug matplotlib, however. We could probably use a debug Python on Travis (in addition to the ones we already have) -- just a matter of installing the python-debug package and using the python-debug executable.
Mike ··· On 04/19/2014 10:53 AM, Jouni K. Sepp�nen wrote: I was prompted by Docs build segfaults on Launchpad · Issue #2916 · matplotlib/matplotlib · GitHub to run some static checkers on the C/C++ extension modules, and I was going to submit some simple fixes as pull requests, including assertions of some preconditions. I just realized that our build system sets the -DNDEBUG compiler flag, which makes sense for release builds but could hide problems in test builds.
Do any of our Travis, Launchpad, or other daily builds undefine NDEBUG? -- Michael Droettboom Science Software Branch Space Telescope Science Institute