summaryrefslogtreecommitdiffhomepage
path: root/make.html.markdown
diff options
context:
space:
mode:
authorven <vendethiel@hotmail.fr>2016-03-12 09:31:02 +0100
committerven <vendethiel@hotmail.fr>2016-03-12 09:31:02 +0100
commit4a4f16bfac0a778083a0d50aa506def9f0bdd104 (patch)
tree8b7b00c6b6ce472a74271a0bb6bd94a484e6b45b /make.html.markdown
parent4ad29330a001bec7f3fe848c8e529c0a5c55aba4 (diff)
parent717f515fcf3c7757447235ed9fa5fbdbfc4848b2 (diff)
Merge pull request #2167 from divayprakash/typos-fix
[make/en] fixed typos and spellings, added content
Diffstat (limited to 'make.html.markdown')
-rw-r--r--make.html.markdown19
1 files changed, 11 insertions, 8 deletions
diff --git a/make.html.markdown b/make.html.markdown
index b3425b8a..ab128475 100644
--- a/make.html.markdown
+++ b/make.html.markdown
@@ -9,16 +9,16 @@ A Makefile defines a graph of rules for creating a target (or targets).
Its purpose is to do the minimum amount of work needed to update a
target to the most recent version of the source. Famously written over a
weekend by Stuart Feldman in 1976, it is still widely used (particularly
-on Unix) despite many competitors and criticisms.
+on Unix and Linux) despite many competitors and criticisms.
-There are many varieties of make in existence, this article assumes that
-we are using GNU make which is the standard on Linux.
+There are many varieties of make in existence, however this article
+assumes that we are using GNU make which is the standard on Linux.
```make
# Comments can be written like this.
-# Files should be named Makefile and then be can run as `make <target>`.
+# File should be named Makefile and then can be run as `make <target>`.
# Otherwise we use `make -f "filename" <target>`.
# Warning - only use TABS to indent in Makefiles, never spaces!
@@ -27,13 +27,16 @@ we are using GNU make which is the standard on Linux.
# Basics
#-----------------------------------------------------------------------
+# Rules are of the format
+# target: <prerequisite>
+# where prerequisites are optional.
+
# A rule - this rule will only run if file0.txt doesn't exist.
file0.txt:
echo "foo" > file0.txt
# Even comments in these 'recipe' sections get passed to the shell.
# Try `make file0.txt` or simply `make` - first rule is the default.
-
# This rule will only run if file0.txt is newer than file1.txt.
file1.txt: file0.txt
cat file0.txt > file1.txt
@@ -99,8 +102,8 @@ process: ex1.txt file0.txt
%.png: %.svg
inkscape --export-png $^
-# Pattern rules will only do anything if make decides to create the \
-target.
+# Pattern rules will only do anything if make decides to create the
+# target.
# Directory paths are normally ignored when matching pattern rules. But
# make will try to use the most appropriate rule available.
@@ -185,7 +188,7 @@ var := hello
var2 ::= $(var) hello
#:= and ::= are equivalent.
-# These variables are evaluated procedurely (in the order that they
+# These variables are evaluated procedurally (in the order that they
# appear), thus breaking with the rest of the language !
# This doesn't work