|
Size: 980
Comment:
|
Size: 2189
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| '''g''' ''filename'' get source (read/only) from SCCS into current directory | '''SCCS Helpers''' |
| Line 5: | Line 5: |
| '''gk''' ''filename'' get source and suppress replacement of identification keywords (see below) in the retrieved text by their value. | * '''g''' ''filename'' get source (read/only) from SCCS into current directory |
| Line 7: | Line 7: |
| '''goarabic''' set build language as Arabic (used by Qt only I imagine) | * '''gk''' ''filename'' get source and suppress replacement of identification keywords (see below) in the retrieved text by their value. |
| Line 9: | Line 9: |
| '''gochinese''' set build language as Chinese | '''Language Specific scripts''' * '''goarabic''' set build language as Arabic (used by Qt only I imagine) |
| Line 11: | Line 12: |
| '''godemo''' switch to demo environment | * '''gochinese''' set build language as Chinese |
| Line 13: | Line 14: |
| '''godev''' switch to top of current development tree | * '''gous''' build using US English |
| Line 15: | Line 16: |
| '''goeng''' reset language control to English | * '''goeng''' reset language control to English |
| Line 17: | Line 18: |
| '''Build options''' | |
| Line 18: | Line 20: |
| '''gol''' signal that we are building Linux text based application. | * '''godemo''' switch to demo environment |
| Line 20: | Line 22: |
| '''gorel''' switch to release mode build | * '''godev''' switch to top of current development tree |
| Line 22: | Line 24: |
| '''goscox''' SCO OpenServer build | * '''gol''' signal that we are building Linux text based application. |
| Line 24: | Line 26: |
| '''gosdb''' build for later use of gdb | * '''gorel''' switch to release mode build |
| Line 26: | Line 28: |
| '''gosql''' build for systems using SQL databases | * '''goscox''' SCO Open Server build |
| Line 28: | Line 30: |
| '''gous''' build using US English | * '''gosdb''' build for later use of gdb |
| Line 30: | Line 32: |
| '''gox''' build using X11 interface | * '''gosql''' build for systems using SQL databases |
| Line 32: | Line 34: |
| '''gox3''' build using Qt version 3.0.4 as opposed to 3.3.5 | * '''gox''' build using X11 interface |
| Line 34: | Line 36: |
| '''k ''modem device port'' ''' launch kermit on modem named | * '''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. |
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.