我可以建议循序渐进的方法。

Visit GNUwin Download the Setup Program Follow the instructions and install GNUWin. You should pay attention to the directory where your application is being installed. (You will need it later1) Follow these instructions and add make to your environment variables. As I told you before, now it is time to know where your application was installed. FYI: The default directory is C:\Program Files (x86)\GnuWin32\. Now, update the PATH to include the bin directory of the newly installed program. A typical example of what one might add to the path is: ...;C:\Program Files (x86)\GnuWin32\bin

我也曾经遇到过同样的问题。但我很惊讶没有找到一个特解。

从GnuWin32或通过winget安装是很好的和简单的选择。但我只找到了3.8.1。这个版本缺少非常重要的选项-O，它在编译多线程时正确地处理输出。

目前，Choco似乎提供4.3。所以我们可以期待最近的版本。

但是也有自编译的选项。如果你必须安装make(用于编译)，这应该是一个有效的选项。

head to https://www.gnu.org/software/make/ and download a version of your liking unpack the tar.gz files (use 7zip and unpack the file twice to retrieve the actual content) navigate to the created directory open command prompt in that directory run build_w32.bat gcc This will start the compilation with the gcc compiler, which you would need to install in advance. When running build_w32.bat without any option they try to use the MSVC compiler. Sidenote: I found it surprising that gnu does not use gcc as default but MSVC :-) ignore the warnings created during compilation. The result should still be fine retrieve your fresh gnumake.exe from the directoy GccRel (when compiled with gcc) put this file somewhere where you like and rename to make.exe add the location to the system variable %PATH%

正如其他人所指出的:如果其他程序也安装了各种make版本，那么这种手动安装可能会导致冲突。

安装Msys2 http://www.msys2.org 遵循安装说明 使用$ pacman -S make gettext base-devel安装make 添加C:\msys64\usr\bin\到您的路径

如果你想使用命令行模拟器cder，一个解决方案可能会有帮助。您可以随意地安装包安装程序。首先，我们在windows命令提示符中使用以下行安装chocately:

@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
refreshenv

在安装了chocolatey之后，可以使用choco命令来安装make。安装完成后，你需要在/ cder /config/user_alias .cmd中添加一个别名。应增加以下一行:

make="path_to_chocolatey\chocolatey\bin\make.exe" $*

然后，Make将在cmder环境中操作。

GNU make可用于巧克力。

从这里安装chocoley。 然后，choco安装make。

现在您将能够在窗口上使用Make。 我试着在MinGW上使用它，但它应该也能在CMD上工作。

除了GNU之外，您可能还需要许多coreutils。Touch, rm, cp, sed, test, tee, echo等等。构建系统可能需要bash特性，如果没有其他原因，通常从进程ID($$$$)创建临时文件名。没有bash是不行的。你可以用Windows上流行的POSIX模拟器得到所有东西:

Cygwin (http://www.cygwin.org/) Probably the most popular one and the most compatible with POSIX. Has some difficulties with Windows paths and it's slow. GNUWin (http://gnuwin32.sourceforge.net/) It was good and fast but now abandoned. No bash provided, but it's possible to use it from other packages. ezwinports (https://sourceforge.net/projects/ezwinports) My current favorite. Fast and works well. There is no bash provided with it, that can be a problem for some build systems. It's possible to use make from ezwinports and bash from Cygwin or MSYS2 as a workaround. MSYS 1.19 abandoned. Worked well but featured very old make (3.86 or so) MSYS2 (https://www.msys2.org/) Works well, second fastest solution after ezwinports. Good quality, package manager (pacman), all tooling available. I'd recommend this one. MinGW abandoned? There was usually MSYS 1.19 bundled with MinGW packages, that contained an old make.exe. Use mingw32-make.exe from the package, that's more up to date.

Note that you might not be able to select your environment. If the build system was created for Cygwin, it might not work in other environments without modifications (The make language is the same, but escaping, path conversion are working differently, $(realpath) fails on Windows paths, DOS bat files are started as shell scripts and many similar issues). If it's from Linux, you might need to use a real Linux or WSL. If the compiler is running on Linux, there is no point in installing make for Windows, because you'll have to run both make and the compiler on Linux. In the same way, if the compiler is running on Windows, WSL won't help, because in that environment you can only execute Linux tools, not Windows executables. It's a bit tricky!