|
DataReel Static Library Kit |
Overview
Environment Files
Makefile Templates
Building With MSVC
Building With BCC32
Building With GCC
Building With HPUX C++
Building With SUN C++
The DataReel static library kit is supplied as an additional component to the open-source library. The static library kit includes all the necessary source code and makefiles to build static libraries for all the currently supported WIN32 and UNIX platforms. The DataReel static libraries are composed of indexed object files that can be linked to your application. Static linking is a process that links the library and executable together forming a standalone executable. Standalone executables start faster then dynamically linked executables and are much easier to distribute because the executable can be launched with no external dependencies. The primary disadvantage of static linking is that the entire executable must be recompiled and redistributed each time the library is updated, changed, or revised. Static and dynamic libraries speed up compile times considerably and allow you organize and manage large projects more efficiently.
Pre-compiled static libraries are available from glNET Software. Additionally glNET Software provides custom-built static libraries, WIN32 dynamic link libraries, and UNIX shared libraries. For more information about obtaining the DataReel static library kit or pre-compiled libraries please contact:
glNET Software
P.O. Box 820314
South Florida, FL. 33082-0314
FAX: 413-622-7705
glnet@glnetsoftware.com
http://www.glnetsoftware.com
The DataReel static library kit is distributed as a zip archive, a compressed tar or gziped tar archive and should be installed in the "lib" subdirectory of the source code distribution. Each supported compiler has a ".env" file located in the DataReel lib directory. Environment files are makefiles used to set all configurable path, compiler, and linker parameters. The environment files included with the static library kit do not require any modifications to build a static library. By modifying one of the following files you can build custom versions of the default libraries.
bcc32.env - Borland C++ 5.5 hpux10.env - HPCPLUSPLUS A.10.27 hpux11.env - HP aC++ B3910B A.03.30 linux.env - gcc version 2.96 20000731 (Red Hat Linux 7.0) msvc.env - Microsoft Visual C/C++ 6.0 SP3 solaris.env - Sun WorkShop C++ 5.0 (4.2 compatibility mode)
A makefile template file is supplied for each supported compiler. Makefile templates are located in the DataReel lib directory and can be used to build applications using the DataReel static libraries with the compiler and linker options set in the compiler's ".env" file. Before using a template file you must set the absolute path to the DataReel library in the template file's $(GCODE_LIB_DIR) variable:
# Setup my path to the gxcode library GCODE_LIB_DIR = #--> Set the absolute path here WIN32 example: GCODE_LIB_DIR = C:\dreel410 UNIX example: GCODE_LIB_DIR = /usr/local/datareel/dreel410
The following is a list of makefile templates included with the static library kit:
template.bcc - Borland C++ 5.5 template.h10 - HPCPLUSPLUS A.10.27 template.h11 - HP aC++ B3910B A.03.30 template.gcc - gcc version 2.96 20000731 (Red Hat Linux 7.0) template.vc - Microsoft Visual C/C++ 6.0 SP3 template.sol - Sun WorkShop C++ 5.0 (4.2 compatibility mode)
The MSVC static libraries have been built using the following compilers and tested on the subsequent WIN32 platforms:
Microsoft Visual C/C++ 4.2 Microsoft Visual C/C++ 6.0 SP3 Windows 95A Windows 95C Windows 98 Windows 98SE Windows NT 4.0 SP4 Server Windows NT 4.0 SP4 Workstation
There are two files used to build Microsoft Visual C++ static libraries and a VC template file used to generate application makefiles. All configurable parameters are contained in the msvc.env include file located in the DataReel lib directory. The msvc.env include file is derived from the %MSVCDir%\include\win32.mak makefile under VC60 and the %MSDevDir%\include\win32.mak makefile under VC40. When building static libraries within the MSVC IDE please refer to the msvc.env $(DEFMACS) variable for the required and optional preprocessor directives. To set the preprocessor directives for your active configuration press Alt-F7 and select the C++ tab. NOTE: If you encounter any run-time errors after building a static library within the MSVC IDE be sure to refer to the compiler and linker set in the msvc.env and win32.mak files.
To build the 32-bit debug and release libraries outside of the MSVC IDE execute the following commands:
C:\>CD C:\dreel410\lib nmake -f msvc.mak FINAL=0 nmake -f msvc.mak clean nmake -f msvc.mak FINAL=1 nmake -f msvc.mak clean
This will generate the "gxcode32d.lib" debug library and the "gxcode32.lib" release library.
To build the 64-bit debug and release libraries outside of the MSVC IDE execute the following commands:
C:\>CD C:\dreel410\lib nmake -f msvc.mak FINAL=0 64BITCFG=1 nmake -f msvc.mak clean nmake -f msvc.mak FINAL=1 64BITCFG=1 nmake -f msvc.mak clean
This will generate the "gxcode64d.lib" debug library and the "gxcode64.lib" release library.
The BCC32 static libraries have been built using the following Borland compilers and tested on the subsequent WIN32 platforms:
Borland C++ 5.5 Windows 95A Windows 95C Windows 98 Windows 98SE
There are two files used to build Borland BCC32 static libraries and a BCC template file used to generate application makefiles. All configurable parameters are contained in the bcc32.env include file located in the DataReel lib directory. When building static libraries within the Borland IDE please refer to the bcc32.env $(DEFMACS) variable for the required and optional preprocessor directives. NOTE: If you encounter any run-time errors after building a static library within the Borland IDE be sure to refer to the compiler and linker set in the bcc32.env file.
To build the 32-bit static library outside of the Borland IDE execute the following commands:
C:\>CD C:\dreel410\lib make -f bcc32.mak make -f bcc32.mak clean
This will generate the "gxcode32.lib" static library. NOTE: There is no 64-bit support for the command line only version BCC version 5.5.
The RedHat static libraries have been built and tested using:
gcc version 2.96 20000731 Red Hat Linux 7.0
There are two files used to build the RedHat static libraries and a gcc template file used to generate application makefiles. All configurable parameters are contained in the linux.env include file located in the DataReel lib directory. When building static libraries within a Linux IDE please refer to the linux.env $(DEFMACS) variable for the required and optional preprocessor directives.
To build the 32-bit static library execute the following commands. NOTE: This example is using an arbitrary DataReel install directory.
% cd /usr/local/datareel/dreel410/lib make -f linux.mak make -f linux.mak clean
This will generate the "libgxcode.a" static library.
To build the 64-bit static library under Linux you must enable the 64-bit preprocessor directives in the linux.env $(64BIT_DEFMACS) variable and set the 64-bit project name in the linux.mak $(PROJECT) variable.
% cd /usr/local/datareel/dreel410/lib make -f linux.mak make -f linux.mak clean
This will generate the "libgxcode64.a" static library. NOTE: When using the gcc makefile template you must enable the 64-bit library $(LIBRARIES) variable.
The HPUX static libraries have been built and tested using:
HPUX 10.20 Native C++ Compiler - HP C++ HPCPLUSPLUS A.10.27 HPUX 11.0 Native C++ Compiler - HP aC++ B3910B A.03.30 HP aC++ B3910B A.03.27 Language Support Library
There are four files used to build the HPUX static libraries and two template files used to generate application makefiles. All configurable parameters are contained in the hpux10.env and hpux11.env include files located in the DataReel lib directory. When building static libraries within a HPUX IDE please refer to the hpux10.env or hpux11.env $(DEFMACS) variable for the required and optional preprocessor directives.
To build the 32-bit static library using the HPUX 10.20 C++ front-end compiler execute the following commands. NOTE: HPUX 10.20 builds require the DCE thread library if any multithreaded components are selected in the hpux10.mak makefile. This example is using an arbitrary DataReel install directory.
% cd /opt/datareel/dreel410/lib make -f hpux10.mak make -f hpux10.mak clean
To build the 32-bit static library using the HPUX 11.0 aCC C++ compiler execute the following commands. NOTE: This example is using an arbitrary DataReel install directory.
% cd /opt/datareel/dreel410/lib make -f hpux11.mak make -f hpux11.mak clean
This will generate the "libgxcode.a" static library.
To build the 64-bit static library under HPUX 11.0 you must enable the 64-bit preprocessor directives in the hpux11.env $(64BIT_DEFMACS) variable and set the 64-bit project name in the hpux11.mak $(PROJECT) variable. NOTE: There is no 64-bit support for HPUX 10.20.
% cd /opt/datareel/dreel410/lib make -f hpux11.mak make -f hpux11.mak clean
This will generate the "libgxcode64.a" static library. NOTE: When using the HPUX makefile template you must enable the 64-bit library $(LIBRARIES) variable.
The Solaris static libraries have been built and tested using:
Sun WorkShop C++ 5.0 in 4.2 compatibility mode Solaris 2.7 Solaris 2.8
There are two files used to build the Solaris static libraries and a Solaris template file used to generate application makefiles. All configurable parameters are contained in the solaris.env include file located in the DataReel lib directory. When building static libraries within a Solaris IDE please refer to the solaris.env $(DEFMACS) variable for the required and optional preprocessor directives.
To build the 32-bit static library execute the following commands. NOTE: This example is using an arbitrary DataReel install directory.
% cd /opt/datareel/dreel410/lib make -f solaris.mak make -f solaris.mak clean
This will generate the "libgxcode.a" static library.
To build the 64-bit static library under Solaris you must enable the 64-bit preprocessor directives in the Solaris.env $(64BIT_DEFMACS) variable and set the 64-bit project name in the Solaris.mak $(PROJECT) variable.
% cd /opt/datareel/dreel410/lib make -f solaris.mak make -f solaris.mak clean
This will generate the "libgxcode64.a" static library. NOTE: When using the Solaris makefile template you must enable the 64-bit library $(LIBRARIES) variable.