File | Edit | View | Templates | Project | Compiler | Run | Windows | Help
Compile creates an object file for the code in the currently selected editor window. Compiler options may be specified in the preferences for a given language (see Global Preferences under the File menu item.) The results of the compile appear in the message window (located at the bottom of the pcGRASP window in the above image). If errors are found, the first error will automatically be highlighted in both the CSD editor window and the message window. Clicking on an error message in the message window highlights the corresponding error in the message window.
Compile and Link creates an executable for the code in the currently selected editor window. Errors are handled in the same manner as described above. Note the GNATMAKE is used for Ada 95 programs to accomplish this. Also, there is no link phase for Java programs, so selecting this option will cause only a compile to occur.
Semantic Check invokes the compiler in such a manner that a file's syntax and semantics are checked, but no object file is generated and no linking is performed. Generation of the CSD performs a syntax check of the code and returns the location of errors. However, if this is not enough information to locate the error, performing a semantic check will often return more information, like what the compiler may have been expecting at a certain location.
Make (requires makefile) excutes the command "make" in the directory of the currently active file. This command requires that a makefile called "makefile" be present.
C Parse Mode sets the parse mode for CSD generation for C programs. They are ordered from slowest and most complete to fastest and least complete. If specified, include files are parsed for macro definitions. If macros are well structures (i.e., looks like legal C code) and there are no macro flags (used to flag conditional compilation), expanding macros and parsing include files is unnecessary. Standard C library headers normally contain only well-structured macros and no macro flags. Local include files may be parsed only if these files contain unstructured macros or macro flags, and the time overhead of parsing other headers, which can be large, can still be avoided.
C++ Parse Mode sets the parse mode for CSD generation for C++ programs. They are ordered from slowest and most complete to fastest and least complete. If specified, include files are parsed for macro definitions. If macros are well structures (i.e., looks like legal C++ code) and there are no macro flags (used to flag conditional compilation), expanding macros and parsing include files is unnecessary. Standard C++ library headers normally contain only well-structured macros and no macro flags. Local include files may be parsed only if these files contain unstructured macros or macro flags, and the time overhead of parsing other headers, which can be large, can still be avoided.
Stop Compile interrupts the compile or link process. WARNING: This works reliably only for Java and GNAT 3.09 using the Cygnus development environment. It will not work reliably for MS-DOS GNAT, the DJGPP implementation of GCC, or GNAT 3.04a for Win95/NT. Note that ix86 GNU GCC comes with GNAT 3.09 and can be stopped reliably.