2 ms·
You can even do just: make in many cases. For example, google: ./configure; make; make install to check out a common method of building packages from so
by fuzztester 1y ago
You can even do just:
make
in many cases.
For example, google:
./configure; make; make install
to check out a common method of building packages from source on Unix.
Done it dozens of times, for packages like Oracle, MySQL, Python, and many others.
Although readymade binary packages exist for many such products, what you get by the above method is a good amount of configurability, for special needs or environments (hence the name of the configure command).
- wahern 1y agoIf you don't specify a target, make builds the first target declared. This is traditionally "all", and it's common to define "all:" as the first target in a Makefile (it doesn't need a recipe--a bare "all:" is okay; you can fully define it later in the file). Alternatively, GNU Make supports the ".DEFAULT_GOAL" variable, which you can define anywhere to set the implicit target. Somewhat confusingly, there's also a special target, ".DEFAULT", which you can define as a catchall; it's run for any requested target that has no definition of its own.
- fuzztester 1y agoyes. also, built-in rules like .c.o as well as similar user-definable ones, are useful.