\r
http://www.fh-wedel.de/pub/fh-wedel/staff/di/lclint/index.html\r
\r
-Edit the makefile "Makefile.os2" and the compile batch "makeos2.cmd" \r
-in the "lclint-?.?\os2" directory. During make execution all important \r
-settings will be written to a config file read by any sub makefile. In\r
-any case you will have to set the variable `$BASEDIR' in Makefile.os2 \r
-and `%base%' in makeos2.cmd according to your setup.\r
+You may want to set the correct date and version to be written into the \r
+lclint.exe binary in the Makefile.os2 file, although it is not strictly \r
+necessary. This should be enough to build the program. During make \r
+execution then some information will be written to a config file read \r
+by the sub makefile in the src/ directory.\r
\r
-Then use the batch file makeos2.cmd from inside the os2/ directory\r
-to build lclint. The options to that batch file are:\r
+Use the batch file makeos2.cmd from inside the os2/ directory to build \r
+lclint. The options to that batch file are:\r
\r
makeos2 [--emx|-e|--gcc|-g|--icc|-i|--oldconf|-o|--test|-t|--package|-p]\r
\r
-Like with make, this batch should be called from inside the os2\r
-directory. The options starting with "e" build LCLint using emx/gcc with \r
-debug code. The letter "g" stands for gcc using the OMF object format \r
-and optimization rather than debug code. For IBMs icc compiler use "i".\r
-Each of the above options will create a new configuration. To continue\r
-a build with an existing configuration use "o". Finally "t" runs the\r
-"quicktest" part of the test suite (other tests are not yet supported).\r
+This batch should be called from inside the os2 directory. The options \r
+starting with "e" build LCLint using emx/gcc with debug code. The letter \r
+"g" stands for gcc using the OMF object format and optimization rather \r
+than debug code. For IBMs icc compiler use "i". Each of the above \r
+options will create a new configuration. To continue a build with an \r
+existing configuration use "o". Finally "t" runs the "quicktest" part \r
+of the test suite (other tests are not yet supported).\r
\r
If you experience problems with the automatic configuration file creation\r
from within Makefile.os2 you may alternatively call makeos2.cmd with the\r
local_constants.h and herald.h files from this directory to have it match \r
your setup.\r
\r
+After building the program you may want to testrun it, using the batch\r
+file `run_lclint.cmd' or go through the test suite using `makeos2 -t'. \r
+Before that you will need to set the environment variables in the \r
+`setenv.cmd' file that is called from the other two batches.\r
+\r
Please, be aware that you need the flex library in order to build lclint.\r
As far as I remember the OS/2 version of flex comes with this library for\r
the emx/gcc compiler. If not, you will easily be able to compile it \r
do this, you will have to get the flex sources from one of the usual \r
ftp sites and compile at least the library. \r
\r
-To compile the flex library using IBM's VisualAge C++ compiler, you only\r
-need to perform the following steps:\r
+To compile the flex library using IBM's VisualAge C++ compiler, you \r
+only need to perform the following steps:\r
\r
- enter the flex source directory.\r
- enter "icc -c -Q -O libmain.c" and "icc -c -Q -O libyywrap.c"\r
-- enter "ilib fl.lib" from the command line (the library must not exist)\r
- and "y", "+libmain.obj+libyywrap.obj" and "<enter>" from the ilib prompt.\r
+- enter "ilib fl.lib" from the command line (the library must not \r
+ exist) and "y", "+libmain.obj+libyywrap.obj" and "<enter>" from the \r
+ ilib prompt.\r
- copy fl.lib somewhere where it gets found, I suggest "ibmcpp\lib".\r
\r
When using emx/gcc you can either produce code using the OMF object format\r
andersk / splint.git / blobdiff