| title |
Dependency Side Effects | Microsoft Docs |
| ms.custom |
|
| ms.date |
11/04/2016 |
| ms.reviewer |
|
| ms.suite |
|
| ms.technology |
|
| ms.tgt_pltfrm |
|
| ms.topic |
article |
| dev_langs |
|
| helpviewer_keywords |
dependencies, side effects |
NMAKE program, dependents |
|
| ms.assetid |
d4e8db25-fdc0-4d73-81ec-1538f2e1b3e8 |
| caps.latest.revision |
11 |
| author |
corob-msft |
| ms.author |
corob |
| manager |
ghogen |
| translation.priority.ht |
de-de |
es-es |
fr-fr |
it-it |
ja-jp |
ko-kr |
ru-ru |
zh-cn |
zh-tw |
|
| translation.priority.mt |
|
If a target is specified with a colon (:) in two dependency lines in different locations, and if commands appear after only one of the lines, NMAKE interprets the dependencies as if adjacent or combined. It does not invoke an inference rule for the dependency that has no commands, but instead assumes that the dependencies belong to one description block and executes the commands specified with the other dependency. For example, this set of rules:
bounce.exe : jump.obj
echo Building bounce.exe...
bounce.exe : up.obj
is evaluated as this:
bounce.exe : jump.obj up.obj
echo Building bounce.exe...
This effect does not occur if a double colon (::) is used. For example, this set of rules:
bounce.exe :: jump.obj
echo Building bounce.exe...
bounce.exe :: up.obj
is evaluated as this:
bounce.exe : jump.obj
echo Building bounce.exe...
bounce.exe : up.obj
# invokes an inference rule
Targets