If you are shipping your application to users who do not have VisualAge C++ installed, make sure that your program can load the VisualAge C++ run-time library on all target machines.
You can use one of following three methods to provide functions and data that your application needs from the VisualAge C++ run-time library:
The easiest way to package an application that links dynamically to the VisualAge C++ run-time libraries is to distribute the Shared Runtime Library. This is also the most efficient solution if your application is large and may run on target machines on which other applications that use the VisualAge C++ DLLs also run. The installation utility provided with the Shared Runtime Library eliminates many of the potential problems of distributing individual DLLs. For example, it never overwrites a DLL with an incompatible version of the same DLL.
However, the Shared Runtime Library is a large package and may not be appropriate if you must minimize the amount of disk space required by one application.
Use the DLL-renaming utility, dllrname, to change the name of individual DLLs. This utility changes all references to a DLL in modules that use it, in addition to changing the name of the file that holds the DLL and all references within that file to the name of the DLL. Choose a new name that is unique for your organization or application. You may ship renamed VisualAge C++ DLLs with your application.
This may be the most efficient solution if your application is large, includes several executable programs that can share the same DLLs, and the target machine is dedicated to your application.
Linking statically does have disadvantages. It increases the size of your modules because each module includes functions and data from the run-time library. It slows the performance because the environment of each instance of the library has to be initialized. Having multiple library environments also makes signal handling, file I/O, and other operations more complicated.
![]()
Run-Time
Environments
The VisualAge C++ Shared Runtime Library
Changing the Name of a DLL
![]()
Build Dynamic Link
Libraries
Choose Your Run-Time
Library
Use the dllrname
Utility
