CRiSP provides various facilities to enable automatic building (make utility), compiling and executing of programs, usually as part of a development environment. The Build/Execute dialog allows you to set up these options so that when the appropriate commands are invoked, CRiSP will know how to perform the desired action.
The following operations are supported:
Make (build) Used to compile up all files in a project and produce one or more output files. This is normally controlled by a makefile script. You do not need to use a makefile and make system. CRiSP lets you define an arbitrary command to be invoked with this facility, so you could use it for any suitable purpose.
Performing a build is usually not a function of the current file you are editing, whereas compiling is.
Compiling Used to convert a program written in a particular source language into some intermediate format, as part of a larger project. Compiling is dependant on the file you are editing at the time the function is invoked. CRiSP allows you to create a macroised command to invoke, the actual command depending on your settings and the file you are editing at the time you invoke the action.
Execute Used to execute an arbitrary program, for example the executable file generated by the make command above.
Parser This is used to specify a compiler so that CRiSP can correctly parse the error and warning messages generated, and hence, correctly locate line numbers in the affected source files. By default, CRiSP contains support for a wide variety of compilers and applications, so you should not need to set this option. If your compiler is listed then use it. If not, then contact support and we will gladly add additional compiler settings. If you do decide to do this, please provide some real life sample error and warning messages so we can do the job properly, along with the compiler name and version information.
All of these functions are available from the Tools menu, and from the toolbar (if the Compile toolbar has been enabled for display).
You can set up the various options using the OptionsBuild/Execute dialog.
The Keyboard & Mouse settings dialog box is used to configure personal preferences for CRiSP regarding the keyboard and mouse operation. These include whether the <Alt> keys pop up dialog boxes or prompts appear on the command line, and whether the mouse should operate in a Unix style or Windows style. The most likely candidate for changing is the function key mappings depending on whether you like dialog boxes or prefer faster keyboard control.
This option allows you to tune how CRiSP uses memory when reading and editing files. Normally you will not need to use this option, but it can be useful under certain special circumstances, e.g. running CRiSP on small systems configurations when you want to edit huge files (files which are too large for RAM or virtual memory address space). Also this option allows you to configure certain safety aspects of file editing – to avoid problems when two or more users edit the same file.
This dialog box allows you to make permanent changes to the defaults used for searching and replacing. When you use the search and replace dialog boxes, you are presented with a similar set of options, but these settings only last for the current CRiSP session. Use this dialog box to make permanent changes so that they persist from one session to the next.
This dialog box is used to configure autosaving and backing up of files. Autosaving is the ability for CRiSP to save files automatically after a period of idle time, or a number of keystrokes. Backups are performed when the file is saved (not as a result of an autosave). The autosave & backup dialog box consists of three parts, selected from a tab setting.
The buffer list dialog box is used to show all the files currently loaded into CRiSP, together with summary information.
The keyword builder is a dialog which allows you to create and modify colorization definitions. A colorizer definition is needed to tell CRiSP how to perform colorization of keywords for files of a particular type. CRiSP comes with a variety of supported languages, but you can use this dialog to create your own or to modify a supplied definition. For example, you might be programming in C and want to add custom function libraries so that they are colored in a different color.
In order to create a colorizer there are three types of things you need to define:
Special parsing characters
This language editing modes configuration is used to specify characteristics of files which are dependent on their type. Normally you deduce the type of a file from the file extension, although, sometimes even this is not sufficient.
There are numerous settings which can be applied to the different file types. CRiSP comes with a selection of default settings, but you are free to extend or modify the list to suit your personal tastes. Click here to see a description of the file extension syntax
The settings dialog consists of two main parts – a tree view of the defined file types on the left, and the attributes on the right. Because there are a number of attributes per file type, they are divided up into sections. Expanding the tree view for a file type shows the relevant sections for that file. Clicking on the appropriate branch will show the settings on the right hand side.
These options allow you to simply configure the external commands used to support the CRiSP RCS commands. CRiSP contains support for a number of standard and third party RCS systems. These are shown in a tree view on the left of the dialog. Selecting one of these will fill in the command profiles for each command.
This dialog box contains various miscellaneous settings.
This category is used for setting up various aspects of the screen. This includes setting the fonts, colors, and enabling or disabling certain GUI parts of the screen (either scrollbars, menu bar, etc.), and what parts of the status line are to be displayed.