Development environments

Visual Lint supports a variety of development environments via both interactive and command line applications, as well as dedicated plug-ins for Microsoft Visual Studio and Eclipse.

 

Supported solution, workspace and project types

Visual Lint can directly analyse codebases using the solution, workspace and project file types shown in the table below:

ExtensionDescriptionInteractive
application
Command line
application
Applicable
Plug-in
.atslnAtmel Studio 6.x solutionYesYesVisual Studio 1
.avrgccprojAtmel AVR Studio 5 projectYesYesVisual Studio 1
.avrslnAtmel AVR Studio 5 solutionYesYesVisual Studio 1
.bdsgroupBorland Turbo C++ Builder 2006 project groupYesYes-
.bdsprojBorland C++ Builder 2006 projectYesYes-
.bpgCodeGear C++ Builder 5.0/6.0 project groupYesYes-
.bpkBorland C++ Builder 5.0 or 6.0 package fileYesYes-
.bprBorland C++ Builder 5.0 or 6.0 projectYesYes-
.cbprojCodeGear C++ Builder 2007/2009/2010/XE/XE2/XE3 projectYesYes-
.cppprojAtmel Studio 6.x C++ projectYesYesVisual Studio 1
.cprojAtmel Studio 6.x C projectYesYesVisual Studio 1
.cprojectEclipse CDT projectYesYesEclipse 3
.dpgAnalog Devices VisualDSP++ 4.0 or 5.0 project groupYesYes-
.dpjAnalog Devices VisualDSP++ 4.0 or 5.0 projectYesYes-
.dspMicrosoft Visual C++ 6.0 projectYesYesVisual Studio
.dswMicrosoft Visual C++ 6.0 workspaceYesYesVisual Studio
.ewpIAR Embedded Workbench projectYes Yes -
.gpjGreen Hills MULTI projectYes 4Yes 4-
.groupprojCodeGear C++ Builder 2007/2009/2010/XE/XE2/XE3 project groupYesYes-
.icprojIntel C++ compiler project (for Visual Studio 2003/2005/2008)YesYesVisual Studio
.metadataEclipse-based workspace (folder)YesYesEclipse 3
.prjCodeVisionAVR projectYesYesVisual Studio 1
.projectEclipse Java projectYesYesEclipse 3
.slnMicrosoft Visual Studio 2002/2003/2005/2008/2010/2012/2013 solutionYesYesVisual Studio 2
.uvprojKeil µVision 4 projectYesYes-
.vcpMicrosoft eMbedded Visual C++ 4.0 projectYesYesVisual Studio
.vcprojMicrosoft Visual C++ 2002/2003/2005/2008 projectYesYesVisual Studio 2
.vcxprojMicrosoft Visual C++ 2010/2012/2013 projectYesYesVisual Studio 2
.vcwMicrosoft eMbedded Visual C++ 4.0 workspaceYesYesVisual Studio

Note that for our purposes the terms "solution", "workspace" and "project group" above refer to the same thing - a collection of projects. Within the software this is generically referred to as a "solution".

 

Available Visual Lint plug-ins

In addition to the interactive and command line applications two dedicated Visual Lint plug-ins are currently available:

Integration/plug-inSupported development environments
Visual Studio plug-in 2
  • Microsoft Visual C++ 6.0 SP6
  • Microsoft eMbedded Visual C++ 4.0 SP2
  • Microsoft Visual Studio .NET 2002
  • Microsoft Visual Studio .NET 2003
  • Microsoft Visual Studio 2005
  • Microsoft Visual Studio 2008
  • Microsoft Visual Studio 2010
  • Microsoft Visual Studio 2012
  • Microsoft Visual Studio 2013
  • Atmel AVR Studio 5 1
  • Atmel Studio 6.0 1
  • Atmel Studio 6.1 1
  • Atmel Studio 6.2 1
Eclipse plug-in 3
  • Eclipse platform 3.4 (Ganymede) or later.
  • CodeWarrior 10.0
  • QNX Momentics 4.7
  • Altera Nios II EDS 13.1

For information on the compatibility of specific Eclipse based environments, Please contact us.

 

1 Atmel AVR Studio 5 and Atmel Studio 6 can load the Visual Studio plug-in, but manual registration is required for it to do so. Please see How do I register the Visual Lint plug-in with AVR Studio 5 or Atmel Studio 6?

2 Due to restrictions imposed by Microsoft Corporation, the Visual Lint plug-in for Microsoft Visual Studio is unable to load in Express Editions of Visual Studio. Codebases generated by Express Edition products can however be analysed by the interactive and command line Visual Lint applications.

3 Eclipse support includes that for compatible Eclipse based embedded environments such as CodeWarrior, QNX Momentics and Nios II EDS. Where appropriate both x86 and x64 installations are supported (when run on a 64 bit system, the installer prompts for the version to install).

4 System include folder properties are not yet read for this format, so in the meantime they will have to be defined manually (e.g. written as -i directives within a PC-lint std.lnt indirect file).

Please contact us if you require support for additional development environments, analysis tools or platforms.



Copyright © 2004 - 2015 by Riverblade Ltd. All rights reserved.