Instructions for installing the Win32 version of LCLint: 


Download http://lclint.cs.virginia.edu/downloads/binaries/lclint-2.5q-win32.zip. 

Unzip the package. This can be done using any unzip utility, such as WinZip. The zip file contains several directories. Extract them to a new directory, for example C:\lclint-2.5q. The lclint binary is in lclint.exe. 

Set environment variables: 
LARCH_PATH - path to search for lclint libraries and initializations files. If you are using the standard directories, this should be ".;C:\lclint-2.5q\lib". 
LCLIMPORTDIR - directory containing lcl imports files. If you are using the standard directories, this is C:\lclint-2.5q\imports. 

CPATH - the pathname used to find system include files (e.g., stdio.h should be found on this path) 

If you are using Windows 95/98/ME, you can set these variables by adding the following lines to your autoexec.bat file: 

     set LARCH_PATH=C:\LCLINT-2.5q\lib
     set LCLIMPORTDIR=C:\LCLINT-2.5q\imports
     set CPATH=<your include file path>
     
These changes will not take effect until you reboot your machine. 
If you are using Windows NT, you can set these variables using the Control Panel | System. Select the Environment tab and enter the Variable and Value. 

If you are using djgpp with Windows 98, please check Daniel Barker's notes on setting this variable. 

If you can't figure out how to set envirnoment variables in Windows, you can instead use the flags -larchpath and -lclimportdir in your lclint.rc file. 

Set up your command PATH to include the directory containing lclint.exe, or move the binary to a directory on your command path. 


Subscribe to the lclint-announce mailing list by sending a message to majordomo@virginia.edu containing the body: 
     subscribe lclint-announce
     
Microsoft Developer Studio
Running in Output Window 
You can add custom tools to Developer Studio to run LCLint within the IDE. Select Tools | Customize. Add a new command to the command list. In the command edit box, enter the command to run lclint (e.g., lclint). In the arguments edit box, enter the command line arguments (e.g., *.c +parenfileformat). Check the Use Output Window box. 
More ambitious users working on large projects, will configure Developer Studio to run lclint on a single file and use an lclint library for interface information. 

Message format 

You can configure LCLint to produce messages that can be parsed by DevStudio by using the +parenfileformat flag. (This is set by default in the Win32 binary.) Since DevStudio wraps message text automatically, you may also wish to use -linelen 999 to set the line length high enough so lclint will not split lines. 
