RSC/MP Programming Manual

Application Development Linking Windows 32-Bit RSC/MP Applications
Linking Windows RSC/MP Applications
RSC/MP applications for Windows should use the RSC/MP API library RSCW32.DLL
(RSCW64.DLL for 64-bit platforms). The corresponding import library is RSCW32.LIB
(RSCW64.LIB for 64-bit platforms). These libraries support the STDCALL calling
convention, which is the standard used by the Windows API DLLs.
Note. Earlier versions of the RSC/MP API library used the CDECL calling convention. For
compatibility with existing applications, RSC/MP provides the RSCNT.DLL run-time library
which supports CDECL. This library will be discontinued in a future version. Application
developers are urged to re-link their application with RSCW32.LIB, in order to use
RSCW32.DLL.
The RSC/MP API library (RSCW32.DLL, RSCW64.DLL or RSCNT.DLL) makes use of
the Piccolo API library (LIBPIPE.DLL or LIBPIPE64.DLL for 64-bit platforms) at
runtime. It is not necessary to reference LIBPIPE.DLL or LIBPIPE64.DLL during the
linking of a Windows RSC/MP application.
Linking UNIX RSC/MP Applications
The RSC/MP UNIX API is a shared library (librsc) which depends on the Piccolo API
library (libpipe). The following list sho ws the RSC/MP library files with their respective
UNIX platform:
RSC/MP API Piccolo API
AIX librsc.o libpipe.o
HP-UX librsc.sl libpipe.sl
HP-UX11i librsc.so libpipe.so
Linux librsc.so libpipe.so
Linux (64-bit) librsc64.so libpipe64.so
Solaris librsc.so.1 (library)
librsc.so (symbolic link)
libpipe.so.1 (library)
libpipe.so (symbolic link)
Solaris (64-bit) librsc64.so.1 (library)
librsc64.so (symbolic link)
libpipe64.so.1 (library)
libpipe64.so (symbolic link)
The shared libraries are needed at build time in order to link the application, and also
at run time as they are loaded when the application is executed. Different UNIX
systems require different options to be passed to the linker when linking with shared
libraries. Please consult the documentation provided with your particular UNIX system
for details.
One common concern is the method by which the dynamic loader will locate librsc
and libpipe at run time. The dynamic loader‘s operation is generally governed by
options that yo u specify whe n linking the executable. For example, the loader could
use a certain environment va riable that can be set up at run time, or it could use an
absolute location where the libraries were located at link time — depending on the
options yo u supply during linking.
HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006
6- 5