Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launcher environment does not include extra CLI paths #4580

Open
slicerbot opened this issue Mar 13, 2020 · 3 comments
Open

Launcher environment does not include extra CLI paths #4580

slicerbot opened this issue Mar 13, 2020 · 3 comments
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@lassoan
Copy link
Contributor

lassoan commented Mar 21, 2020

@jcfr is this still relevant?

@lassoan
Copy link
Contributor

lassoan commented Apr 30, 2020

@jcfr please close or retarget

@lassoan lassoan added this to the Backlog milestone Apr 30, 2020
@jcfr
Copy link
Member

jcfr commented May 5, 2020

Launcher could be improved so that logic of functions extensionLibraryPaths()/extensionQtPluginPaths()/.. found in qSlicerExtensionsManagerModel is also used to temporarily update settings when additional module path are specified.

This should be done before the application starts to ensure the path environment variables are updated before the real Slicer process starts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants