Opening Build Logs

Anytime you build a target, a build log is automatically created. By default it is stored at the root level of the output folder for that target (e.g., [project]\Output\[user name]\[target name]). However, in the Options dialog (File > Options) you can choose where your log file will be stored when you build a target. As an alternative to the default location, you can choose to place it in the Reports folder of the Project Organizer, or you can select a custom location.

A build log file has an .mclog file extension. The next time you generate the target, the old log file is replaced with a new one.

After opening a build log file, you can see more details of any warnings or errors you may have gotten when building the target.

How to Open a Build Log From the Interface

  1. Open the Builds window pane (View > Builds). See Builds Window Pane.
  2. In the grid select the target whose build log you want to open.
  3. In the local toolbar click Open Build Log.

Viewing the Log File

The log file contains the following tabs:

  • Messages Tab This shows compiler messages and warning text. It is essentially a running log of what is happening as the output is generated.
  • Warnings Tab

    Warnings Tab This shows warnings reported by the compiler. Warnings do not prevent the output from being generated. Instead they might be issues that you need to fix (e.g., missing files) or suggestions for improving your output (e.g., accessibility settings). If you do not want to see a particular type of warning in future builds, you can open the Options dialog (File > Options) and use the Build tab to choose the kinds of warnings to ignore. You can also ignore warnings for a particular target by using the Warnings tab in the Target Editor. If you double-click a row in the log file, the file that is shown in the File column is opened so you can deal with the issue. For assistance in fixing warnings and other issues, see General Troubleshooting Tips.

    Warning Use caution when ignoring compiler warnings. Only ignore warnings that you are certain you do not need to receive.

  • Errors Tab This shows errors, which are critical problems that stop the project from building output.