# Latest master does not build in Debug mode

**URL:** <https://discourse.slicer.org/t/latest-master-does-not-build-in-debug-mode/191>\
**Category:** Development\
**Created:** [April 26, 2017, 12:05am UTC](https://discourse.slicer.org/t/latest-master-does-not-build-in-debug-mode/191 "2017-04-26T00:05:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![blowekamp](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/blowekamp/32/1386_2.png) [@blowekamp](https://discourse.slicer.org/u/blowekamp)\
**Post date:** [April 26, 2017, 2:20pm UTC](https://discourse.slicer.org/t/latest-master-does-not-build-in-debug-mode/191/5 "2017-04-26T14:20:25Z")

</div>

Hello,

This is a known issue with SimpleITK and Slicer in debug mode.

When Slicer is compiled in debug mode, it still compiles Python in release mode. There are only a couple libraries which link against Python and the Slicer run time. These are compiles in different modes Debug and Release. SimpleITK lacks the creative code that is in VTK which defines certain preprocessor definitions before including the Python header to mix Release and Debug libraries.

I even have a prototype branch to add the hack to SimpleITK:

> **[blowekamp/SimpleITK](https://github.com/blowekamp/SimpleITK/tree/SIMPLEITK-576_SupportReleasePythonWithDebugSimpleITK)**
>
> Contribute to blowekamp/SimpleITK development by creating an account on GitHub.

> <https://github.com/blowekamp/SimpleITK/commit/0ce47be294da6462434f255622bd62ca792739e9>

If someone is willing continue work on the patch and help with this Slicer specific customization in SimpleITK, that would be wonderful.

-Brad

---

_[View the full topic](https://discourse.slicer.org/t/latest-master-does-not-build-in-debug-mode/191)._