snavigatorFor more information about using Source-Navigator, see its online documentation from its Help menu.
4. In the Build Directory field, click the “...” button and select the build directory for the monop project (see Figure 6).
6. Click the Add Files button to copy the files to the Target Files list. In Figure 7, see the result of moving the files from the Target Files pane to the Project Files pane.
NOTE:
7. Click OK to close the Edit Targetwindow. Click Done to close the Settings window. The target is created. Now you need to debug and compile the program. See Debugging and compiling the monop target.
2. In Build Targets, select monop from the target list. See Figure 8. Click Start.
3. In this tutorial, Source-Navigator generates some errors from the build. For instance, lint needed to have a definition in the source code. See Figure 9.
5. Click the Defines tab. Enter lint in the text entry box. See Figure 11.
3. Click the Build Rules tab to modify the rules for the build. See Figure 12.
4. Because monop is written in C, double-click the C rule. The Build Rules Settingswindow appears, as in Figure 13.
6. Enter the following input in the dialog below the Macro defines pane, replacing <project directory> with your path to the demos\monop directory:_PATH_CARDS= " \ " <project directory>/cards.pck\ ""
9. _PATH_CARDS="\"<build directory>/cards.pack\" " is a macro. To ensure that this change is picked up at compile time, perform a clean build of the monop target project by selecting Tools->Clean Build in the Build window (see Figure 14).A clean build is equivalent to the make clean command.
11. Now, the monop project compiles without errors (see Figure 15).
2. Enter initdeck as the name of the target (see Figure 16).
Click Create. The Edit Target window appears (see Figure 17).
5. Click the Build Rules tab. Double-click the C rule. The Build Rules Settingswindow appears (see Figure 19). Click the Defines tab. Enter lint in the text entry box.
_PATH_CARDS= " \ " <project directory>/cards.pck\ ""
Open a shell window and copy the cards.inp file in the demos\monopdirectory into the build directory (see Figure 20 for an example of the copy command in a Command.com shell window that a Windows NT developer could use; UNIX users would use the cp command in a shell window).
To ensure that the macro changes are picked up at compile time, perform a clean build of the initdeck target by selecting Tools -> Clean Build (see Figure 21).
A shell window opens to build the cards (see Figure 22) and closes after the build is complete.
A shell window opens and monop runs automatically. Enter the number of players and their names. See Figure 23 for an example in a shell window of a project that builds and is ready to run.