This section begins the machine specific information for setting up Open C API
on a Linux system and includes the necessary information you need to create
environment variables and to compile, link, and run your Open C API programs.
Environment variable
Description
UGII_USERFCN
This variable is defined in .ugii_env and points to the NX directory where the
Open C API libraries reside.
Although this variable is defined for you in .ugii_env, you can customize this
variable for your own Open C API environment. For example, you can define
UGII_USERFCN to point to the directory that contains the libraries. On a
typical system, this environment variable points to: ${UGII_BASE_DIR}/ugii.
Currently, the IBM linker cannot accept a library name when you specify a full
path name. To use uflink when specifying libraries use both the "-L" (uppercase
L) and "-l" (lowercase l) options to specify the directory and library name
respectively. For example, if your libraries (mylib1.so and mylib2.so) exist in
the directory "/users/user1", then specify the following:
-L/users/user1 -lmylib1.so -lmylib2.so
If your libraries reside in different directories, then use the -L switch to
specify each directory location. For example, if mylib1.so and mylib2.so reside
in directories "user1" and "user2", then specify the following:
Open C API programs can be run from any of three environments: the operating
system, an NX Open C API interface, or an NX GRIP program.
Unix does not require special run time support for Open C API programs. To run
an external Open C API program, type its name at the unix shell prompt. Any
ASCII terminal can be used to run these programs.
GRIP Open C API Interface
Any task which can be run from the UFUN interface can also execute from a GRIP
program using the XSPAWN command. See the GRIP programmers manual for more
details.