Compiling Camoto v1.x under Windows

Jump to: navigation, search

This tutorial will explain how to set up a compilation environment under Microsoft Windows with Visual Studio 2013 so that a Windows version of Camoto can be compiled from source.

These instructions are for the v1.x (old) version of Camoto. Please consider compiling the master branch instead, so that you can also contribute to ongoing Camoto development!


  • Visual Studio 2013 installed with the C++ compiler available
  • git command-line tools installed, or some other way of checking out git repositories into arbitrary folders

Create source tree

  1. Close the camoto-win32 repository ( into a folder. For this tutorial we will use H:\Camoto, so change as appropriate.
  2. After cloning, confirm you have H:\Camoto\Camoto.sln
  3. Within each project folder, clone the following git repositories into a git folder inside each project folder. You might need to do this from the command line (git clone https://url):
    • H:\Camoto\libgamecommon\git :
    • H:\Camoto\libgamearchive\git:
    • H:\Camoto\libgamegraphics\git:
    • H:\Camoto\libgamemaps\git:
    • H:\Camoto\libgamemusic\git:
    • H:\Camoto\camoto-studio\git:
  4. Confirm the following files are present in the given paths. If so, everything has been placed in the correct folders:
    • H:\Camoto\libgamecommon\git\
    • H:\Camoto\libgamearchive\git\
    • H:\Camoto\libgamegraphics\git\
    • H:\Camoto\libgamemaps\git\
    • H:\Camoto\libgamemusic\git\
    • H:\Camoto\camoto-studio\git\
    • H:\Camoto\Camoto.sln
  5. Double-click on H:\Camoto\Camoto.sln (or open in Visual Studio)
  6. You should now have the Solution loaded for Camoto, with a project for each .dll and .exe file in the project. However it's not quite ready to build yet!

Configure wxWidgets

This step can be omitted if you don't want to build the GUI (Camoto Studio) and are happy working with the command-line tools.

  1. Download the Windows binaries for wxWidgets
    1. Go to
    2. Under the Binaries heading, go to wxMSW DLLs
    3. Download the correct set of binaries for your compiler and the version of wx you want to use. For example if you download wxMSW-3.0.2_vc120_x64_Dev.7z then you will be getting wxWidgets version 3.0.2, for vc120 (Visual Studio 2013), x64 (64-bit), Debug version. You may want different versions or different architectures (see details at the bottom of the list of downloads.) Note there are also downloads that include both 32-bit and 64-bit DLLs.
    4. Go up to the parent directory (link at the top of the list of downloads) and also get the headers, e.g. wxWidgets-3.0.2_headers.7z
  2. Extract the downloaded files somewhere. This guide will use C:\local\wx for both downloads.
  3. Open the Camoto Solution and under the studio Solution Folder, right-click on the camoto-studio project and choose Properties.
  4. Go to Common Properties then wxWidgets.
  5. Set the wxWidgets path to the install folder, i.e. if you have C:\local\wx\lib then put C:\local\wx here.
  6. Change the SHARED' option to Dynamically-linked
  7. Set wxMSVC_VERSION to whatever vc version you downloaded (e.g. 120 for wxMSW-3.0.2_vc120_x64_Dev.7z)


Once wxWidgets is set up, the build process can begin. Be aware that the first time you do this, all the other prerequisites will be downloaded which will take some time, especially for Boost which is quite large and has many files. Approximately 130MB will be downloaded and it will take up around 1GB of disk space once everything has been decompressed.

  1. Right-click on the Solution and choose Build Solution to compile everything.
  2. When the compilation has finished, the output files should be in H:\Camoto\Debug
  3. You will get errors about missing DLLs the first time you run many of the programs. Copy missing DLLs into the Debug folder from the previous step.
    • Copy the Boost DLLs from packages\boost_*\lib\native\address-model-*\xxx.dll in the Solution directory (H:\Camoto). The NuGet packages would normally do this automatically but for some reason the Boost ones don't.


Undefined references

If you get messages about undefined references to png-related functions like png_create_info_struct the the NuGet package for libpng doesn't support your compiler. At the time of writing, this happens with Visual Studio 2013 because the NuGet package hasn't yet been updated for vc120.

The workaround is to:

  1. Go into the Solution directory and into the packages/libpng. folder and edit libpng.targets.
  2. Find the <ItemDefinitionGroup> tags - there are a lot of them. Find all the ones that say v110.
  3. For each one, copy the block (from <ItemDefinitionGroup> until the matching </ItemDefinitionGroup>, including both tags)
  4. In the copy, go to the <ItemDefinitionGroup> line and change vc110 to vc120 in two places. This process is making copies of the Visual Studio 2012 sections and changing them to apply to Visual Studio 2013.
  5. There are more v110 mentions on the <AdditionalDependencies> line. These must be left alone, as we want VS2013 to use the older VS2012 libraries. If you were to change this line too, you'd just get "file not found" errors because there are no libraries for vc120 yet. (This is why the package needs to be updated!)

At present this has to be done for the following packages:

  • libpng
  • glew
  • libxml2
  • libiconv