| Home
| Previous
| Next
| Up

### Setting up Your Compiler Configuration

Once you have installed the source code and compiled the libraries from the command line, you will need inform your compiler where the include files and library files are located for your own projects. The following steps provide a guide to setting things up correctly for your compiler.

After the files are installed, all include files into the %SCITECH%\include directory under the installation directory where you chose to install the product. So if you installed the product in c:\scitech, the include file directory would be c:\scitech\include). If you are compiling your applications from the Integrated Development Environment (IDE) for your compiler, you will need to set the include directories for your project file’s to include the %SCITECH%\include directory.

If you are compiling from the command line, you simply need to add the %SCITECH%\include directory to your INCLUDE path environment variable (or the command line configuration file for your compiler if it doesn’t use environment variables).

When the libraries are built, the library files end up under the %SCITECH%\lib directory under the installation directory where you chose to install the product. So if you installed the product in c:\scitech, the library directory is c:\scitech\lib). Beneath this directory is are debug and release directories, containing debug and release versions of the libraries (depending on what you compiled or installed). Beneath those two directories is a hierarchy of directories containing library files for different operating systems and different compilers as shown in the tables below (there may be more if there are more compilers supported in a particular release):

32-bit DOS protected mode support:
dos32\bc4 | Borland C++ 4.52 32-bit DOS libraries
dos32\bc5 | Borland C++ 5.0 32-bit DOS libraries
dos32\wc10 | Watcom C++ 10.6 32-bit DOS libraries
dos32\wc11 | Watcom C++ 11.0 32-bit DOS libraries
dos32\dj2 | DJGPP 2.01 32-bit DOS libraries

32-bit Windows:
win32\bc4 | Borland C++ 4.52 32-bit Windows libraries
win32\bc5 | Borland C++ 5.0 32-bit Windows libraries
win32\bcb5 | Borland C++ Builder 5.0 32-bit Windows libraries
win32\vc40 | Microsoft Visual C++ 4.0 32-bit Windows libraries
win32\vc50 | Microsoft Visual C++ 5.0 32-bit Windows libraries
win32\vc60 | Microsoft Visual C++ 6.0 32-bit Windows libraries
win32\wc10 | Watcom C++ 10.6 32-bit Windows libraries
win32\wc11 | Watcom C++ 11.0 32-bit Windows libraries

32-bit RTTarget-32:
rtt32\bc50 | Borland C++ 5.0 32-bit RTTarget-32 libraries
rtt32\bcb5 | Borland C++ Builder 5.0 32-bit RTTarget-32 libraries
rtt32\vc50 | Microsoft Visual C++ 5.0 32-bit RTTarget-32 libraries
rtt32\vc60 | Microsoft Visual C++ 6.0 32-bit RTTarget-32 libraries
rtt32\ow10 | Open Watcom C++ 1.x 32-bit RTTarget-32 libraries

32-bit OS/2:
os232\emx | GNU C++ for OS/2 libraries (emx)
os232\va3 | IBM VisualAge for C++ 3.0 OS/2 libraries
os232\va36 | IBM VisualAge for C++ 3.65 OS/2 libraries
os232\wc11 | Watcom C++ 11.0 32-bit OS/2 libraries
os232\ow10 | Open Watcom C++ 1.x 32-bit OS/2 libraries

Linux:
linux/gcc/x86/a | GNU C++ for Linux static libraries (x86)
linux/gcc/x86/so | GNU C++ for Linux shared libraries (x86)
linux/gcc/ppc-be/a | GNU C++ for Linux static libraries (PowerPC Big Endian)
linux/gcc/ppc-be/so | GNU C++ for Linux shared libraries (PowerPC Big Endian)
linux/gcc/alpha/a | GNU C++ for Linux static libraries (Alpha Big Endian)
linux/gcc/alpha/so | GNU C++ for Linux shared libraries (Alpha Big Endian)

QNX:
qnx4/wc10 | Watcom C++ 10.6 for QNX 4
qnx4/wc11 | Watcom C++ 11.0 for QNX 4
Qnxnto | GNU C++ for QNX Neutrino

If you are compiling your applications from the IDE for your compiler, you will need to set the library directories for your project file to include the %SCITECH%\lib\… directory (select the appropriate directory from Tables above). If you are compiling from the command line, you simply need to add the %SCITECH%\lib\… path to your LIB path environment variable (or the command line configuration file for your compiler if it doesn’t use environment variables).

Once you have done the above steps, you should then be able to compile and link your own programs using the SDK.

Note: For Watcom C++ users, by default Watcom C++ compiles all source code using register based parameter passing. Hence by default all SciTech Software libraries are compiled with register based parameter passing. If you are compiling and linking you code for stack based parameter passing, you will need to link with a different set of libraries. All libraries can be compiled with either stack and register based calling. The stack based libraries will have the same name as the register based versions of the libraries, but will have an extra ‘s’ added to the front of the library name. To build or link to the stack call libraries, use the STKCALL=1 option to dmake.

Copyright © 2002 SciTech Software, Inc. Visit our web site at http://www.scitechsoft.com