Build - Log file

The Build - Log file page shows the contents of the most recently generated log file. Tarma QuickInstall generates a log when you issue the Project > Check or Project > Build commands. The log is automatically saved in a file with a name that depends on the build style (see Build style on the Build page):

• Single Exe - The log file has the same file path as the distribution file, but a .log extension.
• Plain Folder - The log file has the same name as the root folder of the distribution tree, but has a .log extension appended. This places the log file in the parent folder of the distribution tree, which is by design because the log file is not intended for distribution.

Note - Existing log files are overwritten without warning whenever a new one is generated. Therefore, if you want to preserve a log file as part of, for instance, the audit trail for your Setup package, you should rename it or copy it to some other location before re-checking or re-building the project.

The contents of the log file should be self-explanatory. However, the following notes may be useful when interpreting log files.

• Diagnostic messages appear in the log file as they do in the Diagnostic messages area, except that the log file uses [i], [!], [x], and >>> instead of the and symbols (in that order) that indicate the severity level of the message in the Diagnostic Messages Area.
• Messages in the log file are not linked to the parts of the project that they refer to; use the Diagnostic messages area if you want to use diagnostic messages to navigate through the project.
• During project builds (but not during project checks), the log file also records detailed information about each installation file included in the distribution package. This information is not sent to the Diagnostic messages area, because it is intended for audit trail purposes only, not for project diagnosis.
• If you checked the Copy Setup.ini to build log box on the Build page, the log file also includes a verbatim copy of the Setup.ini file that is stored in the Setup package. As with the installation information, the Setup.ini copy is solely intended as an audit trail and does not appear in the Diagnostic Messages Area. The Setup.ini file appears between two -------- separator lines in the log file.