Something like InstallShield path variables ?

[juergen.haigis]

Hi,

is there something in IA like the InstallShield PathVariables ? If we want to build two different releases of the same produkt e.g debug build with debug information files included in a separate feature and a release build without debug information files. Wow can I tell IA where to get the files ? Once out of the debug files folder and other out of the release file folder.

Thanks

[CandiceJones]

Yes, compiler variables which are more powerful and versatile. There are various ways you can use compiler variables:

1) To substitute a direct value at compile time. For example, add a variable called PATHVAR in the Project Options -> Compiler Variables, set its default value to c:\\files\\release, and then specify the source path for files in your script using the form #PATHVAR#\\myfile.fil. Tip: Use the Project | Refactor Paths tool to update hard coded path references in your project in a single pass.

2) To selectively include/exclude parts of your setup files and logic. The Compiler Variable If/Compiler Variable Else/Compiler Variable End statements let you test for a particular value of a compiler variable at build time, and include/exclude parts of your MSIcode script, and files, registry keys, logic, or any other settings, at build time. This eliminates the need to use complex automation, and gives you a very rapid way to customize projects at build time.

Either way, you can set values for compiler variables when building from the command line build tool, miabuild.exe, using the form "VAR=VALUE" for each of the variables. So yes, InstallAware has something that can be considered quite a turbo-charged incarnation of InstallShield's path variables.