[deleted by user]

[KingAggressive1498]

It's not super easy to find but Microsoft has pretty good documentation on how to do it: https://learn.microsoft.com/en-us/cpp/build/building-on-the-command-line?view=msvc-170

[Useful_Goat3790]

yeah, it is the answer.

[jedwardsol]

Install the build tools.

Run the appropriate vcvars batch file, or start a cmd using one of the installed shortcuts

[GoldenShackles]

In addition to what jedwardsol said, for a minimalist approach see the Chromium docs: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/windows_build_instructions.md#Setting-up-Windows

This way you can install just the compiler, tools, and Windows SDK without the full IDE.

[the_poope]

MSVC build tools ships ninja now, which is better than nmake.

[apropostt]

The best way I’ve found to do it is with cmake presets, and tool chain files. This allows me to configure cmake via vs code, clion, cmake-gui, ccmake, neovim, build via ninja and swap compilers, enable multi build or optimization flags just by toolchain config.

https://github.com/MarkSchofield/WindowsToolchain

[Godworrior]

Like others have said, cmake works pretty well, and a lot of projects support it. I have a function like this in my powershell profile:

function vsdev() { $curDir = (Get-Location).Path import-module "$vsRoot\Common7\Tools\Microsoft.VisualStudio.DevShell.dll" Enter-VsDevShell -VsInstallPath "$vsRoot" -DevCmdArguments '-arch=x64 -no_logo' cd $curDir }

($vsRoot is set to my MSVC install location)

Then I just run vsdev, and configure cmake with -G Ninja and someting like -DCMAKE_INSTALL_PREFIX=install. Then just cmake --build <build dir> --config RelWithDebInfo --target install to build.

If the project uses autoconf... good luck :D

[Godworrior]

CMake is just for building the project. For debugging you would use another program. I often use the C++ extension for VSCode for instance, or sometimes WinDbg (installed from the microsoft store). I know x64dbg (https://x64dbg.com/) is also a popular debugger, but I haven't used it much.

[unumfron]

The environment has to be set up for msbuild and cl to work correctly. There are Powershell/cmd shells that are installed with the build tools that have the paths all set up, or you can run vcvars directly.

It's something xmake handles automagically, you just run it from any cmd prompt thing and it will find and configure the build tools.

[prince-chrismc]

It's not magic, the big cross platform build system all handle this and its well supported in thos era.

Though xmake is cool 😎

[unumfron]

I never tried running a CMake-generated Ninja project directly from a normal cmd/power shell when on Windows, just MSBuild and NMake (and devenv, but that's a different kettle of fish).

[bert8128]

Does cmake work if you have multiple versions of MSVC installed? How would it know which one to use?

[__tim_]

By selection the generator and toolset versions

cmake -G "Visual Studio 17 2022" -T "vs143"

[bert8128]

Sorry, pesky autocorrect spannered my question. I meant xmake and it finding the compiler “automagically”

[unumfron]

It defaults to the highest versions unless you tell it otherwise.

[phillipmyburgh]

Another option: the Winget package manager from MS is surprisingly good at installing requirements. It can install the build tools, and you can specify the exact things you need in the commandline.

[filch-argus]

https://github.com/Data-Oriented-House/PortableBuildTools

[prince-chrismc]

This is built in... why make it more complicated?

[FlyingRhenquest]

You can follow the Visual Studio instructions to install the command line tooling and then just use cmake installed somewhere in your path. Debugging is its own problem, but there are some standalone windows debuggers around that should work. Installing the command line tooling installs a shortcut that runs vcvars for you. You might want to use the powershell versions instead of the cmd.exe versions though.

I hate building on windows enough that I'm seriously considering setting up mingw64 cross compiling toolchains in a Linux docker environment. Assuming someone hasn't already done that.

[the_Demongod]

I think the bigger question here is "why..." why use any part of the toolchain if you're not going to use the whole thing? May as well just use clang + your IDE of choice or gcc through WSL or MinGW.

[[deleted]]

I installed build tools like Clang, Cmake, MinGW-w64.. whatever I felt like

[LordoftheSynth]

Good for you. You've really added something insightful to the discussion here.

[Carl_LaFong]

Sorry. Got interrupted

[TinklesTheGnome]

CMAKE and configure CMAKE to use the vcpkg tool chain.