Hi guys,
I followed the extension build process here Extensions — 3D Slicer documentation
and got the zip file to work on 5.3 preview before.
Now we have 5.4 stable, I installed it, pull the new source code and rebuilt the application from source, then package the extension again.
When I install the extension from zip file, it was successful (only concern is that the version is NA but I’m not sure how to fix that)
Slicer and extension versions are encoded in folder names in the extension .zip files. Check if they contain the correct versions.
Having NA as extension version may be due to not having the source code of Slicer or the extension under revision control (you must build from a git tree, not from an extacted zip file that you downloaded from github).
Hi Andras,
Thank you for the answer.
I did build 3D Slicer from the git repo. Here is the git log result
This is the git log in our extension repo:
Here is the zip file I got after I built the extension
The file name of the zip file has the hash of the last commit and the date-time as well.
Any other ideas that might be an issue for us?
Thank you very much!
Does the python console indicate any errors loading the module? Maybe the new Slicer version is incompatible with your extension now which is why it worked for you previously, but now no longer.
Does your generated ZIP contain all of the module files that you expect? If not, make sure your CMakeLists files are appropriately including all files to include in the install package. Maybe you changed the organization of files since the previous time when it was working for you with an older Slicer version?
