***************************************************************************** * * * AGD and LEDA * * * * SOURCE CODE INSTALLATION * * * ***************************************************************************** Remark: Starting with AGD version 1.2, the commercial version of AGD is integrated in a LEDA package. The following procedures therefore are an extension of the installation procedure for LEDA. 1. DIRECTORY OVERVIEW: ---------------------- The AGD/LEDA main directory should contain the following files and subdirectories: AGD/Readme.txt information about AGD AGD/Changes.txt most recent changes of AGD (please read !) AGD/Fixes.txt bug fixes since last release of AGD AGD/Install/src.txt this file AGD/Manual/ sources for AGD user manual AGD/man_html/ HTML version of AGD user manual Readme.txt information about LEDA CHANGES (please read !) most recent changes of LEDA FIXES bug fixes since last release LEDA Install/ documentation for installation/usage of LEDA Manual/ sources for LEDA user manual man_html/ HTML version of LEDA user manual license.txt license text lconfig configuration command for unix lconfig.bat configuration command on windows machines Makefile make script confdir/ configuration directory incl/ include directory src/ source files demo/ demo programs demo_cout/ command line demo programs test/ test programs 2. CONFIGURATION FOR UNIX ------------------------- a) Go to the LEDA/AGD main directory b) Type: lconfig [static | shared] where is the name (or command) of your C++ compiler and the optional second parameter defines the kind of libraries to be generated. Note that in the current release shared libraries can be made only for SunOS 5.x (Solaris), Linux, and IRIX. Examples: lconfig CC, lconfig g++, lconfig sunpro shared lconfig without arguments prints a list of known compilers. If you're installing on a windows machine, please read the following sections. 3.1 CONFIGURATION FOR WINDOWS WITH MS VISUAL C++ ------------------------------------------------ a) Setting the Environment Variables for Visual C++: The compiler CL.EXE and the linker LINK.EXE require that the environment variables PATH, INCLUDE, and LIB have been set properly. PATH must point to the \bin subdirectory of your Visual C++ installation, LIB must point to \lib, and INCLUDE to \include. When you installed Visual C++, setup created a batch file, VCVARS32.BAT, containing commands to modify the PATH, LIB, and INCLUDE environment variables. Run VCVARS32.BAT before you compile at the command prompt. VCVARS32.BAT is located in the \bin subdirectory of the compiler. To run VCVARS32.BAT: - At the command prompt, change to the \bin subdirectory of your Visual C++ installation (for instance c:\programs\microsoft developer studio\vc98\bin ). - Run VCVARS32.BAT by typing VCVARS32. b) Go to the LEDA/AGD main directory c) Type: lconfig msc [dll] [ml | mld | md | mdd | mt | mtd] Remark: When building an application with AGD and MS Visual C++, the AGD link library you use depends on which Microsoft C runtime library you intend to link with. Your application code and AGD must both be linked to the same Microsoft C runtime library; otherwise serious linker or runtime errors may occur. The Microsoft C runtime libraries are related to the compiler options as follows C Runtime Library Option LIBC.LIB -ML LIBCD.LIB -MLd LIBCMT.LIB -MT LIBCMTD.LIB -MTd MSVCRT.LIB -MD MSVCRTD.LIB -MDd In order to get the suitable Libs or DLL please choose the corresponding option in the call of lconfig. 3.2 CONFIGURATION FOR WINDOWS WITH Borland C++ ------------------------------------------------ a) Setting the Environment Variables for Borland C++: The compiler BCC32.EXE and the linker TLIB.EXE require that the environment variables PATH, INCLUDE, and LIB have been set properly. PATH must point to the \bin subdirectory of your Borland C++ installation, LIB must point to \lib, and INCLUDE to \include. When you installed Borland C++, setup created a batch file, like BOR54.BAT or BOR551.BAT, containing commands to modify the PATH, LIB, and INCLUDE environment variables. Run this batch file on the command prompt before you compile at the command prompt. The batch file is located in the \bin subdirectory of the compiler. b) Go to the LEDA/AGD main directory c) Type: lconfig bcc [dll] [d] 5. COMPILING: ------------- a) Compiling for UNIX: Type "make" for building the object code libraries (cf. user manual section 1.9) libAGD.a (libAGD.so) AGD library libL.a (libL.so) LEDA basic library libG.a (libG.so) LEDA graph library libG2.a (libG2.so) LEDA semi-dynamic graph library libP.a (libP.so) LEDA d2-geo library libD3.a (libD3.so) LEDA d3-geo library libGeoW.a (libGeoW.so) LEDA GeoWin library libW.a (libW.so) LEDA window library ( *.so if shared libraries are used) Now, follow the instructions given in unix.txt b) Compiling for WINDOWS: Type "make_lib" for building the object code libraries static: libAGD.lib AGD library libL.lib LEDA basic library libG.lib LEDA graph library libG2.lib LEDA semi-dynamic graph library libP.lib LEDA d2-geo library libD3.lib LEDA d3-geo library libGeoW.lib LEDA GeoWin library libW.lib LEDA window library dynamic: libAGD.lib leda.dll leda.lib libGeoW.lib Notice: AGD and GeoWin are currently not available as DLLs. Now, follow the instructions given in win32_lib.txt, respectively win32_dll.txt