Add support for an additional list of environment variables that should be treated as path lists. Add ability to specify these as lists in the manner of [Paths] and [LibraryPaths] (which are merged with any values set in the "traditional" manner for backwards compatibility). Refactor buildEnvironment to treat PATH and the platform-appropriate library path in the same manner as these (which greatly simplifies the code). Besides the added convenience in the configuration file, the generated wrapper script now also prepends to these variables as well as the usual PATH and library path variables.
* The launcher will look up for a file named: /path/to/user/settings/<organizationName|organizationDomain>/<applicationName>AdditionalLauncherSettings[-<applicationRevision>] If such file exists, library paths, paths and env variables settings will be considered. Library paths and paths will be prepended. Env variable behavior can be configured based on the location of the <env:VARNAME> statements. For example: FOO=<env:FOO>:Something or FOO=Something:<env:FOO> * It's also possible to configure the basename of the settings that is lookup. This can be done by settings: userAdditionalSettingsFileBaseName * <organizationDomain>, <organizationName>, <applicationName> and <applicationRevision> are read from launcher settings. For example: [Application] organizationDomain=www.commontk.org organizationName=Common ToolKit name=CTKAppLauncher revision=4810 * If application name is omitted, the following file will be looked up: /path/to/user/settings/<organizationName|organizationDomain>AdditionalLauncherSettings[-<applicationRevision>] * If organization name is omitted, the following file will be looked up: /path/to/user/settings/<organizationDomain>/<applicationName>AdditionalLauncherSettings[-<applicationRevision>] * If both organization name and domain are omitted, the following file will be looked up: /path/to/user/settings/Unknown Organization/<applicationName>AdditionalLauncherSettings[-<applicationRevision>] * If organization name, domain and application name are omitted, the following file will be looked up: /path/to/user/settings/Unknown OrganizationAdditionalLauncherSettings[-<applicationRevision>] * If application revision is omitted, prefix [-<applicationRevision>] will NOT be considered. * Add command line argument --launcher-ignore-user-additional-settings See #10, #8
* Merge NOSPLASH_SHORT_ARG and NOSPLASH_LONG_ARG into NOSPLASH_ARGS * Setting "additionalLauncherNoSplashArguments" is now used instead of "additionalLauncherNoSplashShortArgument" and "additionalLauncherNoSplashLongArgument" * Multiple nosplash arguments can be specified using a comma as a separator
…arameter Now possible to specify where in the splashscreen and the application will be installed. Doing so allow to configure properly the file: <APPNAME>LauncherSettingsToInstall.ini
This macro allows user of the launcher to easily configure two settings file: <APPNAME>LauncherSettings.ini <APPNAME>LauncherSettingsToInstall.ini The user will have to: 1) include the module ctkAppLauncher.cmake 2) call macro ctkAppLauncherConfigure with the xpected arguments