Skip this step if you are building from a WiredTiger release package, and proceed with Building on Windows
First, clone the repository:
Now proceed with Building on Windows
Building WiredTiger on Windows requires CMake as well as the Microsoft Visual C++ compiler in Microsoft Visual Studio 2017.
You can build WiredTiger from source using command-line tools. When compiling via command-line tools, we recommend a prompt/shell that has been appropriately configured with VS toolchain environment variables. We usually recommend using the Visual Studio Developer Command Prompt/Powershell to ensure an appropriately configured environment.
Change directory to the top-level directory, then create and configure a new directory to run your build from:
Change into your newly created build directory and using CMake run the build configuration step to generate your build.
In the absence of an explicit generator, CMake will generate Visual Studio project files (.vcxproj), representing build targets within WiredTiger. To compile the entire WiredTiger project, in the same directory we configured the build, run
msbuild:
To build the python language support, a 64-bit version of Python is required. The required version is referred to as x86-64 on Python.org or x64 on ActiveState Python.
The WiredTiger software consists of a library and a single standalone utility.
WiredTiger's distribution follows the GNU Coding Standards installation guidelines, and by default WiredTiger builds and installs a static library and dll version of the library.
To install WiredTiger:
To install WiredTiger's libraries or binaries into alternate locations, you can use the -DCMAKE_INSTALL_PREFIX
configuration option.
The WiredTiger software supports some additional configuration options:
-DHAVE_ATTACH=1
-DHAVE_DIAGNOSTIC=1
-DNON_BARRIER_DIAGNOSTIC_YIELDS=1
-DENABLE_LZ4=1
-DENABLE_PYTHON=1
-DENABLE_SNAPPY=1
-DENABLE_ZLIB=1
-DENABLE_ZSTD=1
-DWT_STANDALONE_BUILD=0
The WiredTiger CMake build makes available a suite of C/C++ based tests. To run the available tests you can use our smoke test alias (check
). Ensure you're in the build directory and execute:
Alternatively to just run all the tests available:
In addition, to get verbose output with your test run you can use the -VV
flag:
If you want to focus on running a specific test (i.e. run a test that may be failing) you can use the -R
flag: