Installing Burgerlib on a Win32 machine.

Step 1: Copying the SDKs onto your host machine.

Create a folder on your hard drive to copy all of the SDKs that you will be using. The usual place is C:\SDKs but you can place them anywhere you wish.

Once the folder is created, you need to copy and unzip these basic SDKs into their respective folders. The links below will download the current stable versions of the respective folder.

• Burgerlib for Win32 into w32burger.
• DirectX 9 and 10 headers for Win32 into w32directx9.
• Win32 headers from Microsoft for all compilers into w32platformsdk.
• OpenGL for Win32 into w32opengl.
• Quicktime 7 headers for Win32 into w32qt7sdk.

For best use, an environment variable needs to be set up to point to the SDKs directory. The easiest way is to edit your AUTOEXEC.BAT file. Editing your system registry is acceptable as well, but this way it is easier to modify if you decide to move the folder somewhere else.

Insert this line into your C:\AUTOEXEC.BAT file.

 SET SDKs=C:\SDKs

Step 2: Accessing the SDKs from the build environment.

For each target in your Win32 project, you need to add these folders into the include and link include directories so the headers and the libraries can be found. Please note the use of quotes, it will allow the variable $(SDKS) to contain a space.

Include directories for Visual Studio .NET 2003.

In Configuration Properties: C/C++ : General : Additional Include Directories...

 "$(SDKS)\w32burger";"$(SDKS)\w32opengl";"$(SDKS)\w32directx9";"$(SDKS)\w32platformsdk"

In Configuration Properties: Linker : General : Additional Library Directories...

 "$(SDKS)\w32burger";"$(SDKS)\w32opengl";"$(SDKS)\w32directx9"

Access paths for Codewarrior 9.4.

In the menu bar, select Edit : Preferences... : General : Source Trees...
Create the name of "SDKS" and set the path to the folder where the SDKS are.
The typical combination is Name = SDKS and the environment variable is SDKS which usually resolves to C:\SDKS.
For each project, in Settings : Target Settings Panels: Target: Access Paths

    {SDKS}w32burger
    {SDKS}w32opengl
    {SDKS}w32directx9
    {SDKS}w32platformsdk

Step 3: Include the proper library for your target.

Include only one of these libraries for the build target.

Libaries for Visual Studio .NET 2003.

• burgerv71w32dbg.lib for no optimizations and debug information.
• burgerv71w32dbf.lib for full optimizations and debug information.
• burgerv71w32rel.lib for full optimizations and no debug information.

Libaries for Visual Studio .NET 2005.

• burgervc8w32dbg.lib for no optimizations and debug information.
• burgervc8w32dbf.lib for full optimizations and debug information.
• burgervc8w32rel.lib for full optimizations and no debug information.

Libraries for Codewarrior 9.4.

• burgercw9w32dbg.lib for no optimizations and debug information.
• burgercw9w32dbf.lib for full optimizations and debug information.
• burgercw9w32del.lib for full optimizations and no debug information.

Libraries for Open Watcom 1.7.

• burgerwatw32dbg.lib for no optimizations and debug information.
• burgerwatw32dbf.lib for full optimizations and debug information.
• burgerwatw32rel.lib for full optimizations and no debug information.

Go back to the main page.