| title | Formatting the Output of a Custom Build Step or Build Event | 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 |
|
|||||||||||||
| ms.assetid | 92ad3e38-24d7-4b89-90e6-5a16f5f998da | |||||||||||||
| caps.latest.revision | 8 | |||||||||||||
| author | corob-msft | |||||||||||||
| ms.author | corob | |||||||||||||
| manager | ghogen | |||||||||||||
| translation.priority.ht |
|
If the output of a custom build step or build event is formatted correctly, users get the following benefits:
-
Warnings and errors are counted in the Output window.
-
Output appears in the Task List window.
-
Clicking on the output in the Output window displays the appropriate topic.
-
F1 operations are enabled in the Task List window or Output window.
The format of the output should be:
{filename (line# [, column#]) | toolname} :
[any text] {error | warning} code####**:**localizable string
[ any text ]
Where:
-
{a | b} is a choice of either a or b.
-
[
ccc] is an optional string or parameter.
For example:
C:\sourcefile.cpp(134) : error C2143: syntax error : missing ';' before '}'
LINK : fatal error LNK1104: cannot open file 'somelib.lib'