-
Notifications
You must be signed in to change notification settings - Fork 1
Development on Win64
Karn Kaul edited this page Nov 4, 2019
·
3 revisions
LittleEngine offers a few approaches to set up a toolchain on Win64.
- (Win 10) Windows SDK for ninja/MSBuild / Clang/VC++ or MinGW for MinGW / g++
- (Optional) Visual Studio 2019 (to use ninja instead of MSBuild)
- (Optional) LLVM for Win64 (to use Clang/lld instead of MSVC; VS LLVM Plugin will be required if using MSBuild (generating VS solutions))
- (Optional) Git bash / WSL bash to run shell scripts
- Build
LittleEngine/LEDemo/custom executable target:- Run CMake on the top-level
CMakeLists.txtand generate a Visual Studio Solution (eg, atProject_VS). To use Clang (plugin required), enter "LLVM" as the Platform Toolset during configuration. - Open the solution and build
ALL_BUILD. - Debugging:
- Set
Test/LEDemo/ custom executable as the startup project / debugging target.
- Set
- Run CMake on the top-level
- Build
LittleEngine/LEDemo/custom executable target:- Use "Open Folder" and select the directory containing the top-level
CMakeLists.txt.- (Optional) Edit Build Configurations and select
x64-clangas the compiler.
- (Optional) Edit Build Configurations and select
- Build > Build All.
- Debugging:
- Click "Select Startup Item" or the arrow next to the green "play" button and select the built executable
- Use "Open Folder" and select the directory containing the top-level
Note: Visual Studio 2017 ships with CMake 3.12, and does not support using a custom CMake binary;
LittleEnginerequires CMake 3.13, so it is not feasible to build it using VS2017 CMake.
- Follow the instructions on the Linux page, using
MinGW Makefiles(orCodeBlocks - MinGW Makefiles) as the generator.
Note: Even without MinGW, Visual Studio need not be used as an IDE: the build tool just has to run
vcvars64.batto set up its build environment before callingninja/MSBuild.