Introduction to Computer Graphics
CS 445 / 645
Spring 2004

Instructions for Using Extension Libraries on a UVA Grounds Computer

In this course, we make extensive use of libraries that augment the capabilities of the standard C++ and OpenGL tools.  We will be using FLTK to build user interfaces, FLUID to help with user interface design, and GLUT to extend OpenGL.

In order to use these extra tools, our programs need three different types of files: include headers, library files, and dynamic link libraries.  We've precompiled versions of each of these files for you and installed them in a directory structure on blue.unix.virginia.edu. 

Library installation

You must map the directory on blue.unix where the libraries are stored to your local machine.  Use the software installed on the lab machines to map the directory /h1/d/dc/dcb8j/Class/IntroGraphics/UnpackedFiles on blue.unix.virginia.edu to your local machines Q drive.  Your Q drive should contain the following components:

\bin

DLLs and executables

\include

header files

\lib

static libraries and DLL stubs

 

 

You will need to make Visual Studio aware of these directories as 'standard' directories.  For the sake of this example, we will assume you've mapped your Q drive to the blue.unix directory.

In VS6, select Tools - Options - Directories options

In Executable files  add Q:\bin
In Include files add Q:\include
In Library files add Q:\lib

Select "OK"

Execution of your programs may require for the DLLs to actually be in your system path.  Two ways to achieve this is to either copy them in a directory which is on your path (e.g.the windows system32/ directory or, on a lab machine, in the executable's own directory),or to modify your system path accordingly (google search: "setting environment path windows foo," where foo is your windows OS (XP, 2000, etc.). It’s probably going to be accessible from control panel -> system -> environment (or advanced -> environment variables)).

FLUID

You are also going to make heavy use of the FTLK fluid tool.

It can be useful to make it available as an external tool accessible directly from VStudio.  To set up the menu entry for the Fluid GUI tool (recommended):

Select Tools - Customize - Tools

Type "Fluid" on the last line of the command list.

Command Q:\bin\fluid.exe
Arguments $(TargetName)_GUI.fl
Directory $(ProjectDir)

After the fluid external tool is added to this list, count what number it is on the list.  Write this down.

Select "Commands"

Select the "Tools" category.

Drag the #-numbered tool icon on a toolbar of your choice, where # corresponds to what number the Fluid tool is on the external tool list.

Select "Close"

Now you should be able to launch fluid.exe from your Visual Studio programming environment.