Libraries:

If you take it into your head to try compiling any of my code, you will probably need to download and install the following C++ libraries. Depending on what you are trying to compile, you may be able to get away with not installing wxWindows. But one way or another, Boost, DirectX, and IFL tend to sneak into just about all of my code. To get these libraries working in MSVC, you usually just install the package, then go to Tools/Options/Directories and add the obvious /lib and /include directories to the search paths.

wxWindows: A cute little cross platform GUI API. Right now I am only using this in my particle tweak utility. Note that if you want to use wxWindows with OpenGL support, you will need to recompile the whole library with a couple of #defines turned on (which ones will be made obvious when you try to compile any of the opengl sample code). Setting up MSVC to create a new wxWindows project is difficult, so I suggest downloading Bill Nalen's excellent wizard.

IFL: SGI's image format library. I love IFL because it lets me easily read in images in different formats. The image writing routines have given me a bit of trouble through, at the moment I only trust IFL to create 3 channel windows bitmaps. Downloading IFL from SGI's site is a bit of a hassle, if you are feeling lazy you can grab the installer from me.

DirectX: Though I do use OpenGL for graphics, I still use DirectX for things like mouse/keyboard/joystick input and sound. I am still using the old dx7 sdk, though in theory all my code should work if you try to compile it using a newer DirectX version. One strange thing about DirectX is that it tends to only compile properly if you put it's include and lib directories at the top of the directory list in the options menu.

Boost: At the moment I only use boost for its regex libraries, which are wonderful. --You know you always wanted to be able to use perl style regex in C++. Installing boost is pretty easy, just get a copy of the boost libraries, unzip it, and add the boost_1_29_0 directory to your include path. You will need to build the regex libraries after unzipping the files; there are docs on how to do this in the regex subdir.

SvenLibs: An ever growing collection of my own little libraries. Eventually I will probably compile all of these into one .lib and put it up here for distribution. But for now it makes more sense to just include a frozen version of the libraries surrounding any particular project with the source for that project. If you've gotten you hands on one of my dev snapshots, you will need to add dev/include to your include path, and deb/lib to your lib path so that my libraries can compile and link properly.