mirror of
https://github.com/loot/libloot.git
synced 2026-07-27 14:16:01 -07:00
Oliver Hamlet
b9bf9f2e86
The CEF dependency is not resolved using CMake because it's only available behind a CAPTCHA, and the Boost dependency is not resolved using CMake because it is a relatively large dependency that is better shared between LOOT and its dependencies that use it, instead of each having to build a separate copy. This is slower than the existing Travis script, because all targets in the dependencies are now built, but it is more portable.
1.3 KiB
1.3 KiB
Build Instructions using Microsoft Visual C++
These instructions were used to build LOOT using Microsoft Visual Studio 2015 Community, though they should apply to other versions of MSVC.
Boost
bootstrap.bat
b2 toolset=msvc threadapi=win32 link=static runtime-link=static variant=release address-model=32 --with-log --with-date_time --with-thread --with-filesystem --with-locale --with-regex --with-system --with-iostreams
link, runtime-link and address-model can all be modified if shared linking or 64 bit builds are desired. LOOT uses statically-linked Boost libraries by default: to change this, edit CMakeLists.txt.
Chromium Embedded Framework
Most of the required binaries are pre-built, but the libcef_dll_wrapper dynamic library must be built.
-
Configure CMake and generate a build system for Visual Studio by running:
mkdir build && cd build cmake.exe .. -G "Visual Studio 14" -
Open the generated solution file, and build it with
Releaseconfiguration.
LOOT
- Set CMake up so that it builds the binaries in the
buildsubdirectory of the LOOT folder. - Define any necessary parameters.
- Configure CMake, then generate a build system for Visual Studio.
- Open the generated solution file, and build it.