Run this command to install make and all the packages needed to build your code.
sudo apt-get install build-essential
Answer from JorelC on askubuntu.comscripting - How to execute "make; make install" inside a bash script? - Stack Overflow
bash - How to run "make" command in gitbash in windows? - Stack Overflow
Makefile - How to install a bash script into user's bin directory? - Unix & Linux Stack Exchange
go - MINGW64 "make build" error: "bash: make: command not found" - Stack Overflow
Videos
Make is a general purpose workflow program, usually used for compilation. But it can be used for anything.
When you do something like "make all", the make program executes a rule named "all" from a file in current directory named "Makefile". This rule usually calls the compiler to compile some source code into binaries.
When you do "make install", the make program takes the binaries from the previous step and copies them into some appropriate locations so that they can be accessed. Unlike on Windows, installation just requires copying some libraries and executables and there is no registry requirement as such. In short, "make install" just copies compiled files into appropriate locations.
make install does whatever the Makefile author wants it to do. Typically, by this point, it is too late to change the install directory, as it is often known earlier, during the build, so help files and configuration files can be referenced with the correct pathnames.
Many projects use the GNU Autotools to try to improve their portability among hardware and operating system differences. (Different Unix variants use slightly different headers for declarations of functions that are slightly off the usual path -- except most programs need one or another of the ones declared in different locations.)
When a project does use the Autotools, the normal mantra to install it is:
./configure
make
make install
The ./configure typically allows you to use a command line option like --prefix /opt/apache or something similar to specify a different pathname. /usr/local/ is a common default prefix. It is far easier for locally built software to live in one place and distribution-provided software to live in the "main directories": /usr/ /bin/, and so on. (Packagers are very careful to never touch files in /usr/local/ -- they know it is exclusively for system administrators.)
Anyway, the ./configure --prefix /path/to/new/prefix will set a variable in the Makefile that is available when compiling the program, modifying the manual pages so they point to the correct locations for files, modifying configuration files, etc. So make will build the software specifically for the install location you want and make install will install it into that location.
Most programs can run even without the final make install step -- just ./program_name will often start them up. This is definitely a per-project thing -- some, like postfix, qmail, etc., are made up of many different moving pieces and rely on them all working together. Others, like ls or su might be self-contained enough to execute fine from the directory they were built in. (This is not often useful -- but sometimes very useful.)
However, not all projects use the Autotools -- they are huge, complicated, and miserable to maintain. Hand-written Makefiles are much simpler to write, and I personally think just distributing a simple Makefile with configuration variables available is a lot easier on developers and users both. (Though the ./configure ; make ; make install mantra is really easy on users when it works.)
You can also use chocolatey to install it:
choco install make
Here's the package.
Sounds like Make isn't in your git-bash's path.
A quick search shows this guide, which suggests the following steps:
- Go to ezwinports.
- Download make-4.1-2-without-guile-w32-bin.zip (get the version without guile).
- Extract zip.
- Copy the contents to your Git\mingw64\ merging the folders, but do NOT overwrite/replace any existing files.
The guide is several years old. It may behoove you to read some of the comments before taking action.
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.
make is a GNU command, so the only way you can get it on Windows is installing a Windows version like the one provided by GNUWin32. Anyway, there are several options for getting that:
Directly download from Make for Windows
Using Chocolatey. First, you need to install this package manager. Once installed, you simply need to install
make(you may need to run it in an elevated/administrator command prompt):choco install makeAnother recommended option is installing a Windows Subsystem for Linux (WSL or WSL 2), so you'll have a Linux distribution of your choice embedded in Windows 10, where you'll be able to install
make,gcc, and all the tools you need to build C programs.For older Windows versions (Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, or Windows 7 with msvcrt.dll) you can use GnuWin32.
An outdated alternative was MinGW, but the project seems to be abandoned, so it's better to go for one of the previous choices.
GNU Make is available on Chocolatey.
Install Chocolatey from here.
Then,
choco install make.
Now you will be able to use Make on Windows. I've tried using it on MinGW, but it should work on CMD as well.
Run the command:
sudo apt-get install build-essential
Chances are you will need things like gcc to actually do the building so you might as well install those as well. The build-essential package will install other tools used along with make.
sudo apt-get update
sudo apt-get -y install make
(-y = answer 'yes' to any prompts)
Check the installed version:
make -v
I'm trying to install vim with git per the [websites instructions](https://www.vim.org/git.php) and when I try to run "make", git returns "bash: make: command not found". I found a [thread](https://stackoverflow.com/questions/36770716/mingw64-make-build-error-bash-make-command-not-found) about it on stack overflow saying to install and use either chocolatey or ezwinports but I cant get it to work. Can someone help me out please. Its probably something simple I'm doing wrong but I cant seem to figure it out.