# Not all modules are enabled after build

**URL:** <https://discourse.slicer.org/t/not-all-modules-are-enabled-after-build/9644>\
**Category:** Development\
**Created:** [December 29, 2019, 3:23pm UTC](https://discourse.slicer.org/t/not-all-modules-are-enabled-after-build/9644 "2019-12-29T15:23:26Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 30, 2019, 8:14pm UTC](https://discourse.slicer.org/t/not-all-modules-are-enabled-after-build/9644/7 "2019-12-30T20:14:07Z")

</div>

Partially cleaned out build trees and parallel builds are not guaranteed to work. The nightly dashboard shows that clean builds are successful on Windows and Mac (there is a [build error on Linux due to a recent attempt to add sqlite3 to Python](https://discourse.slicer.org/t/import-sqlite-issue-in-slicelet/5691/20), but that should not affect Windows).

Visual Studio Edition should not matter.

What CMake version do you use?  
Do you have any third-party antivirus software installed?

---

_[View the full topic](https://discourse.slicer.org/t/not-all-modules-are-enabled-after-build/9644)._