CONTROL/Software/Scripts
SCCS Helpers
g filename get source (read/only) from SCCS into current directory
gk filename get source and suppress replacement of identification keywords (see below) in the retrieved text by their value.
Language Specific scripts
goarabic set build language as Arabic (used by Qt only I imagine)
gochinese set build language as Chinese
gous build using US English
goeng reset language control to English
Build options
godemo switch to demo environment
godev switch to top of current development tree
gol signal that we are building Linux text based application.
gorel switch to release mode build
goscox SCO Open Server build
gosdb build for later use of gdb
gosql build for systems using SQL databases
gox build using X11 interface
gox3 build using Qt version 3.0.4 as opposed to 3.3.5
Once called these scripts will set various environment variables:
QTDIR, PATH, MANPATH, LD_LIBRARY_PATH, CPLUS_INCLUDE_PATH, OS, REL, EXE, OBJ, OUTERR, SRCDIR, MAIN, OUTPATH, CC, MOC, LIBS, LK, LB, LIBEXT, BIN, UTBIN, LOCALBIN, FLAGS
Utility Scripts
k modem device port launch kermit on modem named
Build.ksh Rather than use standard UNIX Makefiles, most project directories contain a build.ksh file which is responsible for building the project. This file in turn compiles and links using the co, cv, lcv and lnk scripts.
co compiles a source file to object
ccc compiles a standalone program (a program taht contains it's own main() and places the executable in the $BIN directory.
cv compiles and/or links a program to be linked with an object file on the $MAIN directory and places the executable in the $BIN directory.
e.g. cv st ent c creates $BIN/stent from stent*.c in the current directory, but these files are referenced from the ent.c file in $MAIN that is the module containing the main() entry point.