Riverblade - LintProject FAQ

LintProject FAQ

LintProject Pro has now been superseded by Visual Lint Build Server Edition, and new LintProject Pro licences are no longer available. Please see the blogpost LintProject Pro End of Life Notice for support and upgrade details.


On this page you will find answers to some common questions about LintProject Professional. If there is anything you need to know which is not covered here, please do not hesitate to contact us.



Does the LintProject Professional installer include a trial version of PC-lint?

PC-lint does not have a trial version, and therefore we cannot (unfortunately) include it in the LintProject Professional installer. You will therefore need a licenced PC-lint installation in order to use LintProject Professional with PC-lint.

If you need to purchase a copy of PC-lint you can purchase one from us or via a distributor such as PhaedruS SystemS. Please contact Gimpel Software for support and other information regarding PC-lint.

Alternatively, you might want to consider using the CppCheck analysis tool. Although far less thorough than PC-lint, this is an open source tool and can therefore be freely downloaded.


Which operating systems does LintProject Professional support?

LintProject Professional has been tested on Windows 2000 SP4, Windows Server 2003 (SP1 and R2), Windows XP (SP2 and SP3), Windows Vista (RTM and SP1), Windows Server 2008 and Windows 7. Both x86 and x64 installations are supported.

Please contact us if you have any queries about compatibility with a particular operating system or service pack level.


Which solution, workspace and project file types is LintProject Professional compatible with?

The following solution/workspace file types are currently supported by LintProject Professional:

  • Borland C++ Builder 5.0/6.0 project group (.bpg)
  • Borland C++ Builder 2006 project group (.groupproj)
  • CodeGear C++ Builder 2007/2009/XE/XE2/XE3 project group (.groupproj)
  • Microsoft Visual C++ 5.0/6.0 workspace (.dsw)
  • Microsoft Visual Studio 2002/2003/2005/2008/2010/2012/2013/2015 solution (.sln)
  • Microsoft eMbedded Visual C++ 4.0 workspace (.vcw)


The following project file types are supported:

  • Borland C++ Builder 5.0/6.0 package file (.bpk)
  • Borland C++ Builder 5.0/6.0 project (.bpr)
  • Borland C++ Builder 2006 project (.bdsproj)
  • CodeGear C++ Builder 2007/2009/XE/XE2/XE3 project (.cbproj)
  • Intel C++ Compiler project for Microsoft Visual Studio 2003/2005/2008 (.icproj)
  • Microsoft Visual C++ 5.0/6.0 project (.dsp)
  • Microsoft eMbedded Visual C++ 4.0 project (.vcp)
  • Microsoft Visual C++ 2002/2003/2005/2008 project (.vcproj)
  • Microsoft Visual C++ 2010/2012/2013/2015 project (.vcxproj)
  • Texas Instruments Code Composer Studio 3.x project (.pjt)

Please contact us if you require support for a file type not listed above or have any queries about compatibility with a particular environment or service pack level.


Do I have to run LintProject Professional from the installation directory?

No. Although LintProject Professional does use some resources from its installation (notably the message database and a charting component) it can be run from any folder on your system. For example, you may find it useful to copy the LintProjectPro.exe executable into the same folder as the PC-lint or CppCheck executable.

If you prefer to run LintProjectPro.exe from its installation folder, the /toolfolder switch can be used to tell it where to find the PC-lint or CppCheck executable.


Can I pass my own parameters to the PC-lint or CppCheck executable?

Yes. You can use the /param switch to pass parameters directly to the analysis tool.


Help! I'm getting PC-lint analysis errors in the system header files. What could be wrong?

If you are receiving PC-lint errors (as opposed to warnings, elective notes etc.) in the system header files, there is almost certainly a mismatch between your analysis configuration and the configuration presented to the C++ compiler itself. This is most likely to occur if a project configuration is incorrectly handled or the include folder specification is not set up correctly in the std.lnt global indirect file.

The first thing we would suggest is that you incorporate the error suppression files rb-win32-pclint9.lnt (for PC-lint 9.0) and/or rb-win32-pclint8.lnt (for PC-lint 8.0) into your std.lnt file. These files can be downloaded from http://www.riverblade.co.uk/products/visual_lint/downloads/pclint_config_files.zip and contain suppression directives for commonly encountered issues in the Visual C++ header files.

If however you are unable to determine the cause yourself we would be happy to look at your configuration for you and suggest any resultant changes. If you wish to do this, we would ask you to send us the following information:

  • A copy of your analysis configuration (the std.lnt file etc.)
  • A small sample project which illustrates this issue
  • Details of the command line used to run LintProject Professional, showing which configuration was being analysed.


What happened to the original version of LintProject?

It is still available via The Code Project.

"I don't even have pc-lint yet, and the only thing I actually know about it is from reading the ads for it in C++ Users Journal. But thanks to your article, I plan on purchasing a copy in the next few days! Thanks!!"
- Comment posted on the original LintProject article on
The Code Project