Dialogic 6.2 manual Case, November 387

Installation

linking to the DLLs. With the system variable set, you can simply append the absolute path to these files to the Path environment variable.

You can also add the destination location of *.exe files within the merge modules to the system path so that they are executed from anywhere on your system.

	Rather than relying on the Path variable, it is strongly
	recommended that the destination of dynamic_dlls.msm and
	bostsrv.msm be set to [SystemFolder], and the destination of
	dynamic_dlls_x64.msm be set to [System64Folder]. This is especially
	important on a 64-bit version of Windows® using 64-bit applications.
	Examples
	When merging modules into your installation program, you can
	choose from the following cases:
CASE I	Associate multiple merge modules with a single feature (see
	Figure 59). Set the install location of each of the merge modules to
	that feature’s folder property so that changing the install location of
	the feature also affects the associated merge modules. For example:
	1. Create Feature 1 with a folder property of
	{FEATURE1_INSTALL_LOCATION}.
	2. Set the locations of all the merge modules that this feature
	contains to:
	{FEATURE1_INSTALL_LOCATION}
	These settings apply any change to this folder location to all the
	modules set to the original location. If you intend to install one of the
	merge modules in a different location, you must create a second
	feature and associate the module with the feature as shown in
	Figure 60.
CASE II	Create a feature for each merge module. Figure 60 shows an example
	of this case.
CASE III	Install the module as a required hidden feature when you don't want
	to expose the merge module to your user.

November 2009 387