Talk:Adding a Custom Build Tool

1. append to "In Commands, enter the commands that the tool is to execute. For example, perl $(inputfilename). You can use any of the macros that are displayed in the Macros field." this additional clarification:

Most commonly the argument to a custom tool will be $(InputFileName), which is the full path to the file in your project which you've associated with this custom tool.

---

2. Need to describe the "Output File" edit box as follows:

"Output File" is optional and specifies any files that may be output by the custom build tool which will be used for dependency checking. For example, suppose the custom tool command is "midl.exe $(InputFileName) /cstub $(InputName).c", which runs the Microsoft IDL compiler on $(InputFileName) and outputs a file with the same name but a ".c" extension. Adding "$(InputName).c" in the "Output File" edit box will ensure that the command is only run when the output file is out of date with respect to the input file.

---

3. It would also be nice to know how to "unassociate" a custom build tool with a file: Select the file in the project manager. Go to the object inspector. Enter a blank value in the "Custom Build Tool" property.

4. We should mention that .pas files are not eligible for custom build tools because they always are part of a Delphi or C++Builder project and are handled exclusively by the Delphi compiler.

Done

Thanks for your comments! I have incorporated them into the topic.

KrisHouser 20:44, 29 July 2010 (PDT)