11 Distributing Your C++ Products
Distribute your products in such a way that your customer does not need to use the HP aC++ compiler or driver. That is, only distribute executables and shared libraries.
If you write code in HP aC++ and distribute any of the following C++ files to your customers, read the following sections for recommendations and legal requirements.
•Shared libraries containing C++ code with the exception of the following libraries:
◦ /usr/lib/hpux##/libCsup.so
◦
◦
◦
◦
/usr/lib/hpux##/libCsup11.so
/usr/lib/hpux##/libstd.so (and libstd_v2.so)
/usr/lib/hpux##/librwtool.so (and librwtool_v2.so)
/usr/lib/hpux##/libstream.so
where ## is 32 or 64, which are provided as part of the
•Executable files produced by HP aC++ and applications that use shared libraries provided with HP aC++.
•Object files produced by HP aC++.
•Archived libraries containing C++ code.
•Any combination of the above.
NOTE: If you choose to distribute archive libraries or object files, your customer must have purchased HP aC++. Be sure your customer has read this distribution information.
This chapter discusses the following topics:
•“Applications that use HP aC++ Shared Libraries” (page 195)
•“Linking Your HP aC++ Libraries with Other Languages” (page 196)
•“Installing your Application” (page 196)
•“HP aC++ Files You May Distribute” (page 196)
•“Terms for Distribution of HP aC++ Files” (page 197)
Applications that use HP aC++ Shared Libraries
Following lists the HP aC++ runtime libraries that are shipped as part of the
•/usr/lib/hpux##/libCsup.so
•/usr/lib/hpux##/libCsup11.so
•/usr/lib/hpux##/libstd.so and libstd_v2.so
•/usr/lib/hpux##/librwtool.so and librwtool_v2.so
•/usr/lib/hpux##/libstream.so
•Libraries in /usr/include/hpux##
where ## is 32 or 64, which are provided as part of the
Applications that use HP aC++ Shared Libraries 195