• Home
  • Raw
  • Download

Lines Matching refs:be

5 to be a comprehensive document of kati or GNU make. This explains some random
6 topics which other programmers may be interested in.
26 when you changed a single C file. To be fair, things were not that bad. There
28 they ignore dependencies between modules, they are fast. However, you need to be
29 somewhat experienced to use them properly. You should know which modules will be
30 affected by your change. It would be nicer if you can just type "make" whenever
36 project for this. Kati was planned to be a short-term project. Another option
54 Go's performance would be somewhat interesting topic. I didn't study the
60 them will be never freed. IIRC, this kind of allocation pattern isn't good for
85 bottleneck. This would be a very Android specific characteristics. Android's
92 Then either executor or ninja generator will be used. Either way, kati runs its
108 caching the parsed results, kati will be two times slower for Android's
146 the second line will turn out to be a command.
157 Anyway, as a line starts with a tab character can be either a command statement
241 have some forms and should be parsed after evaluating expression by the third
242 parser. This will be discussed in the next section.
255 content of the variable *$(A)* will be *$(info world!)* after the first
258 immediately. So "Hello," will be output and the value of *$(B)* will be an empty
259 string ($(info ...) returns an empty string). Then, "world!" will be shown when
264 keep the type of the original variable. Evaluation of them will be done
272 rule statement can actually be the following four things:
283 A rule is something like *all: hello.exe*. You should be familiar with it. There
321 to build *target*, *echo nospace* should be executed.
326 define variable which can be referenced only from commands in a specified
339 be used even in build commands of prerequisite targets.
356 However, *CFLAGS* for *hello* won't be used when you build only *hello.o*:
361 Things could be even worse when two targets with different target specific
362 variables depend on a same target. The build result will be inconsistent. I
382 optimization only for this function and $(wildcard ...) in commands seem to be
396 ninja generation mode. This will be described later.
431 Multiple rules without commands should be merged into the rule with a
448 target specific variables and some special variables (e.g., $< and $@) should be
548 but nothing is ready to be used as of writing.