The Launcher application provides easy access to all of the tools, documentation, configurations, and examples bundled with Vortex OpenSplice.
The Launcher’s content is populated based on the environment variables available at the time it is started. If the command line is used then the correct release script must be sourced from the Vortex OpenSplice home directory before starting the Launcher.
Unix and Linux
Source the release.com file from the shell command line to set up the Vortex OpenSplice environment.
To start Launcher, enter the following command in the shell:
ospllauncher
Windows
Open an Vortex OpenSplice Command Prompt and enter the following command:
ospllauncher.bat
You can also start Launcher from the Windows Start Menu, which will set the environment variables of the Vortex OpenSplice instance appropriately.
Unix and Linux
In the terminal where the ospllauncher file was executed, enter CTRL+C, or close the Launcher application windows using the X button.
Windows
Close the Launcher application windows using the X button.
Launcher starts up with incorrect, missing, or no content at all
Check the following:
If previous versions of Vortex OpenSplice were used with Launcher, verify that USER_HOME.olauncherprefs does not contain any overridden values pointing to non-existent directories or files.
Launcher starts up but cannot compile or clean example code
Ensure that you have permissions to modify the permissions of OSPL_HOME/examples and any user-specified configuration directories, or start Launcher with elevated privileges.
Launcher starts up but cannot save edited configuration files opened in Configurator that has been started from Launcher
Ensure taht you have modify permissions in the OSPL_HOME/etc/config/ directory, or start Launcher with elevated privileges.
Launcher starts up but cannot write log files
Ensure that you have modify permissions in the OSPL_HOME/ and its subdirectories, start Launcher with elevated privileges, or start ospllauncher from a non-write-protected directory.