Go to ezwinports, https://sourceforge.net/projects/ezwinports/files/
Download make-4.2.1-without-guile-w32-bin.zip (get the version without guile)
- Extract zip
- Copy the contents to C:\ProgramFiles\Git\mingw64\ merging the folders, but do NOT overwrite/replace any exisiting files.
Go to ezwinports, https://sourceforge.net/projects/ezwinports/files/
Download make-4.2.1-without-guile-w32-bin.zip (get the version without guile)
- Extract zip
- Copy the contents to C:\ProgramFiles\Git\mingw64\ merging the folders, but do NOT overwrite/replace any exisiting files.
You can also use Chocolatey.
Having it installed, just run:
Copychoco install make
When it finishes, it is installed and available in Git for Bash / MinGW.
Error installing CmdStan (Windows 10; Command 'mingw32-make.exe' not found @win/processx.c:983)
Can't compile using mingw.
[R]Command 'mingw32-make.exe' not found @win/processx.c:994
Complete newbie: Getting 'make' is not recognized as an internal or external command, operable program or batch file. | Qt Forum
Videos
Hi,
I've recently started programming in university and we're using vscode with the mingw compiler for Windows (I'm using Linux in class so I didn't run into this problem until now) but I've ran into an issue with the compiling.
https://i.imgur.com/2I4M2Ul.png
mingw32−make : The term 'mingw32−make' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ mingw32−make
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (mingw32−make:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Can anyone help me fix this?
I've changed the path in the windows environmental thing and mingw is installed where it is supposed to be as far as I know.
I'm stuck on the installation process of CodeLite (IDE) and MinGW (GCC). Fairly new to learning C++ and the code won't execute.
The code won't build & execute on CodeLite and I get the following errors -
'make' is not recognized as an internal or external command, operable program or batch file (CodeLite)
No targets specified and no makefile found (when I search for the 'make' on Command prompt)
And when I try to build and execute on CodeLite -
3. This app can't run on your PC (MinGW error)
What should I do? I'm no computer whiz, I don't know why I keep getting these errors, I spent my whole day trying to solve this by searching on google but I couldn't-
In Windows10, I solved this issue by adding C:\MinGW\bin to Path and then called it using MinGW32-make not make.
This is an old question, but none of the answers here provide enough context for a beginner to choose which one to pick.
What is make?
make is a traditional Unix utility which reads a Makefile to decide what programs to run to reach a particular goal. Typically, that goal is to build a piece of software from a set of source files and libraries; but make is general enough to be used for various other tasks, too, like assembling a PDF from a collection of TeX source files, or retrieving the newest versions of each of a list of web pages.
Besides encapsulating the steps to reach an individual target, make reduces processing time by avoiding to re-execute steps which are already complete. It does this by comparing time stamps between dependencies; if A depends on B but A already exists and is newer than B, there is no need to make A. Of course, in order for this to work properly, the Makefile needs to document all such dependencies.
A: B
commands to produce A from B
Notice that the indentation needs to consist of a literal tab character. This is a common beginner mistake.
Common Versions of make
The original make was rather pedestrian. Its lineage continues to this day into BSD make, from which nmake is derived. Roughly speaking, this version provides the make functionality defined by POSIX, with a few minor enhancements and variations.
GNU make, by contrast, significantly extends the formalism, to the point where a GNU Makefile is unlikely to work with other versions (or occasionally even older versions of GNU make). There is a convention to call such files GNUmakefile instead of Makefile, but this convention is widely ignored, especially on platforms like Linux where GNU make is the de facto standard make.
Telltale signs that a Makefile uses GNU make conventions are the use of := instead of = for variable assignments (though this is not exclusively a GNU feature) and a plethora of functions like $(shell ...), $(foreach ...), $(patsubst ...) etc.
So Which Do I Need?
Well, it really depends on what you are hoping to accomplish.
If the software you are hoping to build has a vcproj file or similar, you probably want to use that instead, and not try to use make at all.
In the general case, MinGW make is a Windows port of GNU make for Windows, It should generally cope with any Makefile you throw at it.
If you know the software was written to use nmake and you already have it installed, or it is easy for you to obtain, maybe go with that.
You should understand that if the software was not written for, or explicitly ported to, Windows, it is unlikely to compile without significant modifications. In this scenario, getting make to run is the least of your problems, and you will need a good understanding of the differences between the original platform and Windows to have a chance of pulling it off yourself.
In some more detail, if the Makefile contains Unix commands like grep or curl or yacc then your system needs to have those commands installed, too. But quite apart from that, C or C++ (or more generally, source code in any language) which was written for a different platform might simply not work - at all, or as expected (which is often worse) - on Windows.
Most MinGW have a mingw32-make.exe file but no make.exe. Simply copy that and rename it or change the call from make to mingw32-make in your build.
It took me about three hours to resolve this problem. Finally, I realized that all Windows programs are installed in C:\msys64\ucrt64\bin folder. So I searched for ucrt64 make and found mingw-w64-ucrt-x86_64-make. Installing it saved my life.
Try mingw32-make instead.
Use this command to find out which one you're running:
for %i in (make.exe) do @echo. %~$PATH:i
It's basically the equivalent of which for Windows, assuming you know the extension. If you want a script that will check all extensions, you can find it here.
As pointed out in a comment by Chris, latter versions of Windows (Vista, 2003 Server, and Win7, I think) actually have a real equivalent called where, which may be better. Those of us still stuck back on XP can use the command above (or the big script at the other end of that link).