View Issue Details

IDProjectCategoryView StatusLast Update
0002857Slicer4Core: Base Codepublic2013-01-15 13:02
ReporterfbudinAssigned Tomillerjv 
Status assignedResolutionopen 
Product VersionSlicer 4.2.2-1 
Target VersionFixed in Version 
Summary0002857: CLI environment variable

Slicer could set an environment variable when starting a CLI module. This environment variable could give the PATH of the executable. This would allow CLI modules to know where it is and in the case of an Extension to know where it is installed.

TagsNo tags attached.




2013-01-15 13:01

administrator   ~0007676

We discussed this at project week with Bill and Jim - here's my summary:

1) The slicer install directory in the SLICER_HOME environment variable. This can get you to anything that ships with slicer.

2) But an executable extension may be installed somewhere outside the slicer tree. For this, you should look at argv[0] to find the path.

3) When and extension CLI is running as a shared library, it currently doesn't have useful information in argv[0] so there's no good way to find out.

As a solution to point 3, we discussed adding the correct path info when the module entry point is invoked.



2013-01-15 13:02

administrator   ~0007677

I'm assigning this to Jim, since he seemed to indicate that he liked this solution. However it may be better to sign it over to Jc, since he was writing the shared library back end that would work with the new CTK CLI code.

Issue History

Date Modified Username Field Change
2013-01-07 14:26 fbudin New Issue
2013-01-07 14:26 fbudin Status new => assigned
2013-01-07 14:26 fbudin Assigned To => pieper
2013-01-15 13:01 pieper Note Added: 0007676
2013-01-15 13:02 pieper Note Added: 0007677
2013-01-15 13:02 pieper Assigned To pieper => millerjv