Extensions are not working when building Slicer from scratch

[cpinter (Csaba Pinter)]

@fpsiddiqui91

download the extension packages

You cannot use factory-built extensions with your locally built Slicer. In that case you’ll need to clone and build the extensions you want to use.

See also for example

Loadable module crashing binary Slicer

I have an error with my loadable module. I’ve built the Slicer stable version (revision 26489) and I’ve built my module against it without errors. The module works as intended when I launch the built Slicer version. However, if I try to launch module with the binary Slicer release (downloaded from the website, the 4.8.0 version - same as the built revision) the Slicer crashes before opening and I get the following error: “terminate called after throwing an instance of ‘H5::DataSpaceIException’” …

or

Compiled App whichs source pulled from git cannot download extension due to reversion not match.

Problem report for Slicer 4.11.0-2019-05-01 win-amd64: [please describe expected and actual behavior] I compiled the Slicer reversion of “28202” which was pulled from github, and it’s reversion became “aae6a8c”, so that I can’t download extension from Extensions Manager online. The message from Extensions Manager says as below: “No extensions found for win:64-bit, revision: ‘aae6a8c’. Please try a different combination” After that I installed a SlicerVR extension, and it works well. Then I m…