Compilation & Linking procedures

Compilation has been facilitated by the use of two batch command files qfall, qfor. These batch files automatically update the necessary libraries involved in the linking phase. Qfall is the recommended procedure to be used to ensure complete consistency within the SusiQ image. The linking Qlink is performed with the help of dedicated batch and FORTRAN programs to make this operation more environment independent.

F All these command files require that you issue them from your working directory and that loadsq <dev> has been performed.
Compilation & linking tools table

QFALL	Generates the necessary include files from file.ACQ, file.EQU, file.CST, Compiles all the FORTRAN sources in the current directory and inserts them into the user object library QUSER.LIB It is the standard command for generating a brand new version of SusiQ.
QLINK	Link SusiQ using the QUSER.LIB and the SusiQ system libraries. Creates a file sqlink.tmp which is used as the batch file for the real LINK command.
QFOR module	Compile and insert the given module into QUSER.LIB in the current working directory. Can replace qfall and save time if the user knows what he is doing. But it is generally preferable to run qfall in any case to make sure that the new SusiQ image file will be consistent.
SQHARD <interface_name>	Compile the KCS or DSP routines and insert them in the susiq library. Must be done during the installation of SusiQ for the full SusiQ package. (See User Customized SusiQ section )

Examples Compilation &Linking