# Module is not registered on Windows/Linux nightly built

**URL:** <https://discourse.slicer.org/t/module-is-not-registered-on-windows-linux-nightly-built/10060>\
**Category:** Development\
**Tags:** build\
**Created:** [February 1, 2020, 1:32pm UTC](https://discourse.slicer.org/t/module-is-not-registered-on-windows-linux-nightly-built/10060 "2020-02-01T13:32:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shanshan](https://avatars.discourse-cdn.com/v4/letter/s/cdc98d/32.png) [@shanshan](https://discourse.slicer.org/u/shanshan)\
**Post date:** [February 1, 2020, 1:32pm UTC](https://discourse.slicer.org/t/module-is-not-registered-on-windows-linux-nightly-built/10060/1 "2020-02-01T13:32:01Z")

</div>

Slicer Ver 4.11 2020-01-31 on Windows  
Slicer Ver 4.11 2020-01-31 on Mac  
Slicer Ver 4.11 2020-01-30 on Linux

I am having trouble with loading a module we coded last summer into the nightly built of Slicer on Windows and Linux, though there is no problem with loading the module on Mac.  
The error we got was simply saying the module is not registered without no further details entailed.

Note that this module can be loaded without any problems on Slicer Ver 4.11 2019-08-29 of any OS.

Has anything changed for Linux and Windows nightly built over the past few months that we should be aware when developing our own module?

Thank you so much for your time and help!

---

<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:** [February 1, 2020, 1:41pm UTC](https://discourse.slicer.org/t/module-is-not-registered-on-windows-linux-nightly-built/10060/2 "2020-02-01T13:41:40Z")

</div>

If this is a CLI or loadable module (not a Python scripted module) then you need to build your module with _exactly_ the same Slicer version as the one you want to use it with.

If you use exactly the same source code version, compiler version, build options, Qt version, etc. to build Slicer on your computer as the official build computers use then your module will even work with official Slicer builds. Any difference may cause ABI incompatibility and is expected to make your module fail to load or the application to crash.