#MSYS2 CMAKE COMMAND NOT FOUND INSTALL#
#MSYS2 CMAKE COMMAND NOT FOUND UPDATE#
#MSYS2 CMAKE COMMAND NOT FOUND CODE#

Don't close this window yet we'll need it later. Just run this shortcut, and you'll be greeted with a black console window that contains all the necessary setup in order to run command-line Visual Studio tools. Or something like this, as it also depends on the language version of your system. One of those shortcuts is called: Visual Studio 2017/Command line for 圆4 Native Tools for Visual Studio 2017 I'm always installing it to C.Īfter installing, Visual Studio will provide some convinient shortcuts in the glorious Start menu (which is apparently more important than the kernel itself). So I'm not sure it's worth splitting the installation to two drives.

#MSYS2 CMAKE COMMAND NOT FOUND INSTALL#

One fun fact during installation of Visual Studio is that you better install it on your C drive, because if you'll select some other drive, it will still mostly install itself on C drive. I won't provide you with a direct link to Microsoft's site, because any link pointing to them dies faster than a hope for humanity after watching YouTube, that's why I'll just simply link to a DuckDuckGo search query, and you should be able to find the proper link on the first page (hopefully it will be the first link, but with DuckDuckGo you'll never know). And it contains all the tools we need, skipping all the tools we don't need. So the first step is to install Visual Studio Community edition, because it's free. The approach taken in this note is to install Visual Studio, open its command-line tools window that allow you to use command-line Visual Studio tools, snapshot its environment, and re-create this environment in your ~/.bashrc from MSYS2. I'm sure you can find more arguments for it ). You have to work using Visual Studio, but you're not a Windows person, You're interested in how different compilers generate assembly from your C++ source, Make the project compilable on different compilers, like GCC, Clang and Visual Studio, This has several advantages, but mostly it's convinient if you're forced to either: But since we're on Windows, we can do better, and we can actually hack our way into integrating Visual Studio with MSYS2 shell, so we'll be able to use Visual Studio's development tools directly from MSYS2.

#MSYS2 CMAKE COMMAND NOT FOUND CODE#

It's easy to install MinGW's gcc with pacman, as well as clang so you can proof-test your C++ code with different compilers. So, after installing MSYS2 you're going to need a development environment. I've lost patience, aborted WSL session and promised myself to look into this after a year.

#MSYS2 CMAKE COMMAND NOT FOUND UPDATE#

(one trick: MSYS2 also allows you to run sshd, and you'll be able to ssh into your Windows boxes the same way you can ssh on your Linux machines)Īnother solution would probably be WSL (Windows Subsystem for Linux), but honestly last time I've checked the state of this, a simple ls -la took 2 seconds everytime it was run, and apt-get update took probably half of an hour of constant disk swapping. Of course it's not as fast as a native Linux shell, but still it's better than nothing. It's a msys/cygwin-like shell that effectively provides you with a bash shell, and this runs on Windows. One solution is to use MSYS2 environment. The problem is when one is forced to use Windows when it's clear that those goals are incompatible with the person's goals. Unfortunately, Windows doesn't offer any decent command-line oriented environment, because well, it has different goals, and that's understandable. Using Windows is a painful experience for a command-line oriented person like me.

Msys2 cmake command not found