Making a Visual C++ v 5.0 project for the Improv library

  1. know where the include directory for the source files is located, e.g.: c:\user\craig\improv\include
    This directory contains all of the necessary header files for the library.

  2. know where the source directory is located, e.g.: c:\user\craig\improv\src
    This directory contains all of the necesary source files which will be compiled into a single library file.

  3. know where you want the library file to go, e.g.: c:\user\craig\improv\lib\improv.lib
    This is the file which will be made ultimately by the project. It is used to compile programs by linking to the library which will find the compiled definition of functions needed in the programs.
  1. open Visual C++ version 5.0

  2. menu: file --> new --> projects --> Win 32 Static Library: give project a name and location, e.g.: name: library, location: c:\user\craig\sig\projects This will set up a static library project in the specified directory.

  3. menu: build --> set active configuration --> Win 32 Release This step will make the library useable.

  4. menu: project --> settings --> C/C++ --> project options: add /D"VISUAL" and /I"c:\user\craig\sig\include". The "VISUAL" define is needed by the library source code and the include files to determine which compiler is being used to compile the library (uses LINUX on linux computer for example)

  5. menu: project --> settings --> library --> output name: rename to where you want the library to go. most likely: ..\..\lib\improv.lib, but you can put is anywhere you like as long as you remember where it was placed.

  6. menu: project --> add to project --> files: go to src directory, and add all files in the directory . This places the source files into the project making them ready to be compiled into the library file.

  7. build the library (which will be called for example: c:\user\craig\lib\improv.lib) menu: build --> F7

  8. The library should now be created. If it didn't work, you can try sending e-mail to craig@ccrma.stanford.edu since he is familiar with most the the errors that can be generated and what they might mean.
craig@ccrma.stanford.edu