Environment Path Variables
InstallShield 2016
Project • This information applies to the following project types:
Environment path variables enable you to define your own path variables based on certain values on the Environment dialog box.
To view the Environment dialog box:
|
1.
|
Right-click My Computer and click Properties. The System Properties dialog box opens. |
|
2.
|
On the Advanced tab, click Environment Variables. |
A common scenario where environment path variables may be useful is when performing a build from the command line. If you do nightly builds on a machine dedicated to that purpose, you may need to change the path variables from the command line. As long as you use environment path variables, you can define the paths to your project’s files from either a batch file or the command line. These paths are evaluated when the installation project is built, and the correct paths to the files will be used.
Using Environment Path Variables
After you have created an environment path variable, you can use it every time that you add a source file to your project. For example, you might create a variable called <MyFiles> and have it point to C:\Work\Files. If you add a source file to your project that contains that variable’s path in its destination, it is recommended that you use the variable rather than hard-coding the path. This recommendation is displayed in the Path Variable Recommendation dialog box.
To have InstallShield automatically recommend path variables, select the Always display the Path Variable Recommendation dialog to me option on the Path Variables tab of the Options dialog box.
Tip • To override the value of a user-defined path variable, an environment variable, or a registry value for a particular release at build time, use the Path Variable Overrides setting on the Build tab for that release. To learn more, see Overriding the Value of a Custom Path Variable for a Release.
See Also
Path Variables View
Open topic with navigation