Factory extensions with built custom SlicerApp_APPLICATION_NAME

Development
1

Hi guys, we’ve finally surrendered and started to build Slicer for our application (GeoSlicer - petrophysics area). I’ve had success in building it with Windows and adding the customizations needed on the source code. We’ve cloned the oficial repo and based our changes on the commits of the stable releases i.e., we’ve created a branch from 002be18 for the 4.11.20200930 build
I’ve forced the slicer revision to be able to download the factory extensions with

Slicer_FORCED_REVISION "29402"

I believe it is Ok to do that, as long as we keep the changes mostly aesthetical and/or small modifications we could use the factory extensions with no problem. The problem arose when I tried to use a custom App name:

set(SlicerApp_APPLICATION_NAME "GeoSlicer")

We had a problem with SlicerJupyter, for example. The extension could not load because of some paths containing GeoSlicer instead of Slicer. I’ve added some paths to the .ini file and could load the extensions, but had some other issues down the road.

It would be nice to have the extensions available for users, no matter the appname, but we can understand if compiling them is the only option. Do you have any other idea that can make it work?
Thanks

2

Quick question:

Did you use the custom application template to create your custom app, or did you modify Slicer directly?

Also, if you could share some error messages indicating the paths that are not loading correctly, that would be great.

3

I’ve modified Slicer directly. I guess I was asking for trouble. Let me try SlicerCAT and report back. Thanks

4

So the custom app template is the recommended method, but it is also possible that we need to make some modification to SlicerJupyter to have it work nicely with a custom app.