This document describes how to build SUMO under MS-Windows using only freely available (this does not mean "open source") tools. Instructions on how to build SUMO on Windows using an Open Source toolchain are included in our building on Linux pages. Please note that You may also download pre-build Windows binaries.
Please read the whole document before you start, there are some detours and shortcuts included.
If you do not need the GUI, you can skip everything concerning Fox. If you do not need precise geodata conversion, you can skip everything concerning GDAL, Proj.
- Download Visual C++ Express Edition. If you are using Windows 8 or later be sure to download Visual Studio Express for Windows Desktop. Please install all the available Service Packs for Visual Studio as well.
- Download Python for Windows and install it. Our most preferred version is Python 2.7.x for the 32 bit platform, but you may try Python 3 and / or 64bit as well.
- Download and extract sumo-src-svn.zip or a different version (or use a repository checkout, see Downloads)
- Note on installation paths: MSVC seems to have difficulties with include and library paths containing spaces (for instance C:\Program Files). Thus try to avoid installing SUMO or any of the libraries in such paths.
There are two ways of telling the SUMO build where to find its libraries. Either via environment variables or by editing a config file. This document only describes the latter (easier) way, for details on the former and also on how to use different versions and additional libraries see Installing/Windows_Libraries.
- Download the Xerces-C and Fox prebuilt binaries, libraries and headers and extract them.
- For Win32 build with Visual Studio 2013 you currently need the Xerces-C binaries and the Fox toolkit binaries
- They are build for Visual Studio 2013, but may be used with earlier versions as well. You may need to install the Visual C++ 2013 Runtime Distributable for running SUMO then (tested with Visual Studio 2010).
- Download the binary packages for PROJ and GDAL provided at http://www.gisinternals.com/release.php
- For Win32 build with Visual Studio 2013 you currently need http://download.gisinternals.com/sdk/downloads/release-1800-gdal-1-11-3-mapserver-6-4-2.zip and http://download.gisinternals.com/sdk/downloads/release-1800-gdal-1-11-3-mapserver-6-4-2-libs.zip
- Create a new directory and extract both files into that dir (if you download 64bit as well, create a separate dir and extract them there)
- Execute <SUMO>\tools\build\pythonPropsMSVC.py
- Edit the generated <SUMO>\build\msvc10\config.props and enter the paths of all the directories above. An example may look like this:
<?xml version="1.0" encoding="utf-8"?> <Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup Label="UserMacros"> <XERCES>D:\behr_mi\lib\xerces-c-18.104.22.1682</XERCES> <PROJ_GDAL>D:\behr_mi\lib\release-1800-gdal-1-11-3-mapserver-6-4-2</PROJ_GDAL> <FOX16>D:\behr_mi\lib\fox-1.6.52</FOX16> <OSG>$(OSG)</OSG> <FFMPEG>$(FFMPEG)</FFMPEG> <PYTHON_LIB>C:\Python27\libs\python27.lib</PYTHON_LIB> <PYTHON_DEBUG_LIB>C:\Python27\libs\python27.lib</PYTHON_DEBUG_LIB> <PYTHON_INCLUDE_DIR>C:\Python27\include</PYTHON_INCLUDE_DIR> <XERCES_64>D:\behr_mi\lib\xerces-c-22.214.171.1242_64</XERCES_64> <PROJ_GDAL_64>D:\behr_mi\lib\release-1800-x64-gdal-1-11-3-mapserver-6-4-2</PROJ_GDAL_64> <FOX16_64>D:\behr_mi\lib\fox-1.6.52_64</FOX16_64> <OSG_64>$(OSG_64)</OSG_64> <FFMPEG_64>$(FFMPEG_64)</FFMPEG_64> <PYTHON_64_LIB></PYTHON_64_LIB> <PYTHON_64_DEBUG_LIB></PYTHON_64_DEBUG_LIB> <PYTHON_64_INCLUDE_DIR></PYTHON_64_INCLUDE_DIR> </PropertyGroup> </Project>
- Add all directories containing dlls (XERCES\bin, PROJ_GDAL\bin, FOX16\lib) to your PATH or copy the dlls into a directory which is in your PATH.
- If you build for 64 bit and for 32 bit be sure that you add both dirs and that you add the 64 bit dir before the 32 bit dir.
- If you installed all libraries and edited the config.props (or defined the environment variables) correctly there is no need for further configuration and you can skip to the build section.
- The Visual Studio build is configured using .props files in the build/msvc10 subdirectory. If you change some settings which should apply to all subprojects, be sure to edit those files (either with a text editor or the property manager of Visual Studio) and not the project configuration (.vcxproj).
- Even if you generated the config.props as above, you can still define the places of the includes and libraries via environment variables (just refer to them as in the example above). If you want to disable certain features, set the config entry to the empty string. Everything but Xerces is optional, but without Fox it is not possible to build the GUI related projects.
- Open the project <SUMO>\build\msvc10\prj.sln and build the configurations you need.
- For some additional emission tools you need to open <SUMO>\build\msvc10\tools.sln and build them as well
- You will find the results in <SUMO>\bin
- If you plan to extend SUMO yourself, or just want to know whether everything compiled OK, it is strongly recommended to have a look at Developer/Tests. This tool makes it easier to check whether some existing functionality was broken by the extensions.
Linker reports something similar to "LINK : fatal error LNK1104: cannot open file 'C:\Program.obj'"
You probably have installed a library to a path containing white spaces in its name. In such a case, the according environment variable should be embedded in quotes (").
Example: set FOX="D:\my libs\fox-1.6.36".
Failure on pre-build event
If Visual Studio reports a failed pre-build event you can safely ignore this, unless you are building from the subversion repository. In this case you should probably install Python. Even if python is installed the file associations may be broken which causes the generation of src/version.h via tools/build/version.py to fail. Either repair your file associations or undefine HAVE_VERSION_H in src/windows_config.h
The release build is used for the distribution of sumo. The Fastbuild is suitable for frequent recompilation and the Debug build allows all debugging features. Keep in mind that Texttest usually picks up the release build.
- Release: All optimizations, assertions disabled, no debugging symbols, links against external release libs
- Fastbuild: Fewer optimizations, assertions disabled, debugging symbols included, links against external release libs
- Debug: No optimizations, assertions enabled, debugging symbols included, links against external debug libs
Naming Conventions: 64bit executables have the same name as their 32bit counterpart. The Debug build additionally carries the suffix 'D' whereas the Fastbuild uses the 'F' suffix.