Make: Difference between revisions
From wikinotes
No edit summary |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Makefiles are automation built around shellscripts,<br> | Makefiles are automation built around shellscripts,<br> | ||
they are normally used to | they are normally used to manage compilation of C/C++ projects, but can be used for anything. | ||
= Documentation = | = Documentation = | ||
| Line 8: | Line 8: | ||
| Gnu Makefile conventions || https://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html | | Gnu Makefile conventions || https://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html | ||
|- | |- | ||
| Text Function Reference (ex: <code>($shell ..) $(patsubst ..)</code>)|| https://www.gnu.org/software/make/manual/html_node/Text-Functions.html | | Text Function Reference<br>(ex: <code>($shell ..) $(patsubst ..)</code>)|| https://www.gnu.org/software/make/manual/html_node/Text-Functions.html | ||
|- | |- | ||
| Automatic Variables (ex: <code>$@, $<</code>) || https://www.gnu.org/software/make/manual/html_node/Automatic-Variables.html#Automatic-Variables | | Automatic Variables (ex: <code>$@, $<</code>) || https://www.gnu.org/software/make/manual/html_node/Automatic-Variables.html#Automatic-Variables | ||
| Line 32: | Line 32: | ||
|- | |- | ||
| [[make basics]] | | [[make basics]] | ||
|- | |||
| [[make syntax]] | |||
|- | |||
| [[make conventions]] | |||
|- | |- | ||
| [[make examples]] | | [[make examples]] | ||
| Line 38: | Line 42: | ||
</blockquote><!-- Notes --> | </blockquote><!-- Notes --> | ||
= Other = | |||
<blockquote> | <blockquote> | ||
{{ TODO | | |||
expand in the ''syntax'' section, and remove from here | |||
}} | |||
== make builtins == | == make builtins == | ||
<blockquote> | <blockquote> | ||
| Line 141: | Line 94: | ||
</blockquote><!-- echo variable --> | </blockquote><!-- echo variable --> | ||
</blockquote><!-- Other --> | </blockquote><!-- Other --> | ||
Latest revision as of 13:34, 6 September 2021
Makefiles are automation built around shellscripts,
they are normally used to manage compilation of C/C++ projects, but can be used for anything.
Documentation
Gnu Makefile conventions https://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html Text Function Reference
(ex:($shell ..) $(patsubst ..))https://www.gnu.org/software/make/manual/html_node/Text-Functions.html Automatic Variables (ex: $@, $<)https://www.gnu.org/software/make/manual/html_node/Automatic-Variables.html#Automatic-Variables
Tutorials
university of maryland tutorial http://www.cs.umd.edu/class/fall2002/cmsc214/Tutorial/makefile.html mrbook tutorial http://mrbook.org/blog/tutorials/make/
Notes
make usage make basics make syntax make conventions make examples
Other
TODO:
expand in the syntax section, and remove from here
make builtins
gnu-make has a subset of commands that you can use within your makefile.
See excellent documentation: https://www.gnu.org/software/make/manual/html_node/Text-Functions.html .
@command # run cli-command $(shell command) # assign output of cli-command to var $(subst from,to,text) $(patsubst %.c,%.o,file1.c file2.c file3.c) # '%' is a wildcard match. '%'s value is preserved in replacement $(var:pattern=replacement) # single variable pattern-replacementcreate directory
Occasionally, it makes sense to specify the creation of directories in your makefile. (such as creating a /bin directory that can be put in .gitignore). You can do this with the following snippet:
BINDIR = bin dummy_build_folder := $(shell mkdir -p $(BINDIR))
echo variable
Sometimes it's handy to try to figure out just what exactly your compiler is running. You can do this. using a prefix of
@runs a shell command.all: @clear @echo "_INCL: $(_INCL)" @echo "_SRCDIR: $(_SRCDIR)"
