Skip to content

Commit 0ae7b1f

Browse files
Merge pull request #35 from LearnYouSomeComputer/ch5
Make: Os's edits
2 parents dc1b21f + 851a5b8 commit 0ae7b1f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

05-Building-with-Make.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22

33
## Motivation
44

5-
Wow. You've made it six chapters through this book. And probably some appendices too. And yet you have made not one sandwich. Not one!
5+
Wow. You've made it four chapters through this book. And probably some appendices too. And yet you have made not one sandwich. Not one!
66

77
Let's fix that. Time for a classic pastrami on rye.
88
You go to fetch ingredients from the refrigerator, but alas! It is empty.
9-
Someone else has been eating all your sandwiches while you were engrossed in regular expressions.
9+
Someone else has been eating all your sandwiches while you were engrossed by a thorny bash script.
1010

1111
You hop on your velocipede[^bike] and pedal down to the local bodega only to discover that they, too, are out of sandwich fixin's.
1212
Just as you feared --- you are left with no choice other than to derive a sandwich from first principles.
@@ -134,7 +134,7 @@ Of course, doing all this by hand would be awful...which is why we have `make`!
134134
When you run `make`, it looks for a file named `Makefile` or `makefile` in the current directory for a recipe for building your code.
135135
The contents of your `makefile` determine what gets made and how.
136136

137-
Most of what goes in a `makefile` are *targets*: the names of files you want to create.
137+
Most of what goes in a `makefile` are **targets**: the names of files you want to create.
138138
Along with each target goes one or more commands that, when run, create the target file.
139139

140140
For example, let's say you want to build an executable named `program` by compiling all the C`++` files in the current directory.
@@ -220,7 +220,7 @@ However, `make` expects targets to generate files, so if you make a target named
220220
it's possible for `make` to get a little confused.
221221
You don't want to generate any new files, and you don't want to lie to `make` because you're an honest upstanding citizen.
222222

223-
Fortunately, `make` supports targets that don't produce files through something called *phony targets*.
223+
Fortunately, `make` supports targets that don't produce files through something called **phony targets**.
224224
You can tell `make`, "Hey, this target doesn't actually produce a file; just run the commands listed here whenever I ask you to build this target,"
225225
and `make` will be like, "Sure thing, boss! Look at me, not being confused at all about why there's no file named `clean`!"
226226

0 commit comments

Comments
 (0)