Fastgraph/Image Compilation and Linking

Fastgraph/Image programs use the same compilation and linking techniques described in Chapter 2 of the Fastgraph 6.0 User's Guide. The only difference is that you must specify the appropriate Fastgraph/Image library, unit, or module name in addition to those required by Fastgraph. The rest of this section describes how to do this for each supported programming language.

For C and C++ programs, use the following table to determine the appropriate Fastgraph/Image library that corresponds to each Fastgraph library. Then specify both library names in your project file or on the compile/link command line. Like Fastgraph, Fastgraph/Image uses separate libraries for creating DirectX programs.

For example, if you're using Fastgraph/Image with C++Builder, you would link with FGWBC32.LIB plus FGIWBC32.LIB if creating a native Win32 program. Similarly, you would link with FGWBC32D.LIB plus FGIWBCDD.LIB if creating a DirectX program.

For Delphi programs, add the unit file FGIWin to your program's uses statement (FGIWinD if creating a DirectX program). The uses statement must include both the Fastgraph and Fastgraph/Image unit names.

For Visual Basic programs, add the module file FGIWin.bas to your project (FGIWinD.bas if creating a DirectX program). The project must include both the Fastgraph and Fastgraph/Image modules. You may not distribute the Fastgraph/Image Visual Basic module (.bas) files.

For PowerBASIC programs, add an #INCLUDE metastatement specifying the FGIWin.inc include file (FGIWinD.inc if creating a DirectX program). You may not distribute the Fastgraph/Image PowerBASIC include (.inc) files.