Open ihnorton opened 5 years ago
Related to #52.
It would be nice to have an implicit mode like --launch prog <all these arguments are passed to prog>
. I guess this would be a breaking change, so we would need to use something other than --launch
.
-h
is a "special case", looking at the SlicerLauncherSettings.ini
file we have:
[General]
[...]
additionalLauncherHelpShortArgument=-h
additionalLauncherHelpLongArgument=--help
[...]
This means we should probably be ignore the additionalLauncherHelpShortArgument
and additionalLauncherHelpLongArgument
value when --launch
is passed ?
Also, most of the argument to the launcher are namespaced (starts with --launcher-*
), I think issue is specific to -h
and --help
.
The following calls work:
$ ./Slicer --launch ../python-install/bin/python --version
2.7.13
$ ./Slicer --launch python --version
2.7.13
$ ./Slicer --launch ../python-install/bin/python -c "import os; print(os.__file__)"
/home/jcfr/Projects/Slicer-Qt5-VTK9-RelWithDebInfo/python-install/lib/python2.7/os.pyc
$ ./Slicer --launch python -c "import os; print(os.__file__)"
/home/jcfr/Projects/Slicer-Qt5-VTK9-RelWithDebInfo/python-install/lib/python2.7/os.pyc
As far as I understand, it should allow to pass further arguments only to the launched binary, but: