Teach Yourself Borland C++ in 14 Days - portal

6
184 Day 6
TIP
The keyboard shortcut for Make is Ctrl+F9.
The Build All option takes the longest to perform. This option compiles every unit in the
project regardless of whether it has changed since the last build. After compiling all units,
C++Builder links the entire project. So far we have been letting C++Builder add units to our
projects. Further on down the road you may have to do some hand editing of your source files
to add headers and other needed directives. You may even end up editing the makefile. From
time to time, you know, things can get goofed up (we all make mistakes). Performing a Build
All will bring everything up-to-date so you can better sort out any problems you might be
running into. Sometimes a Build All will resolve compiler and linker errors without requiring
you to do anything further.
TIP
Any time you get unexpected (out of the ordinary) compiler or linker
errors, first try a Build All. It could just be that something is out of
sync, and a Build All may cure it. If performing a Build All doesn’t fix
the problem, you’ll have to go to work figuring out where the problem
lies.
Regardless of the method chosen to compile the project, if errors are detected the compile
status dialog box will report There are errors. and will list the number of errors that were
detected as well as any warnings. Figure 6.9 shows the compile status dialog box after errors
are detected.
Figure 6.9.
The compile status
dialog box showing
warnings and errors.
After you click OK to dismiss the compile status dialog box, the Code Editor will come to
the top with the first error line highlighted. The message window at the bottom of the Code
Editor is displayed, and the errors and warnings are listed there. After a successful Compile
Unit, Make, or Build All you can immediately run the program via the Run button if you
choose.