- Does Linticator support PC-lint Plus?
- Can I add more than one Custom Lint File file to a project's configuration?
- What information about the compiler does Linticator use to generate the project configuration?
- Can I use PC-lint on Linux?
- Where can I change the Linticator console font?
- Can I exclude specific source files?
- Configuration Troubleshooting Guide
Does Linticator support PC-lint Plus?¶
Yes, Linticator supports PC-lint Plus, with one caveat: the msg.xml file that Linticator asks for during configuration needs to be manully generated:
./pclp64_linux "-dump_messages(file=msg.xml, format=xml)"
You can use the generated file in the configuration wizard.
Can I add more than one Custom Lint File file to a project's configuration?¶
.lnt files can be added to the Custom arguments section.
What information about the compiler does Linticator use to generate the project configuration?¶
Linticator uses Eclipse CDT's information about compiler includes and symbols:
All these includes and defines are passed to PC/Flexe-Lint.
Can I use PC-lint on Linux?¶
Yes, you can. PC-lint runs under Linux with Wine, all you need is a wrapper script that calls wine with pc-lint, like:
#!/bin/sh /usr/bin/wine /opt/pc-lint/lint-nt.exe $* | tr '\\' /
And then use this script as the "Lint executable" in the configuration entry.
Where can I change the Linticator console font?¶
The Linticator Console uses the same font settings as the debug console, so you can change its appearance under Window → Preferences → General → Appearance → Colors and Fonts → Debug → Console Font.
Can I exclude specific source files?¶
If you have source files in your project that you want Lint to ignore, you can exclude them via the Resource Configurations menu in the file's context menu.
You can see and configure (e.g. with a wildcard match) all the excluded resources in the Paths and Symbols settings of your project:
Alternatively, Lint has two options to mark header and implementation files as library code. The flags are +libh(filename.h) for headers and +libm(C:\filename.c). Note that for libm you need to specify the full path to the file, otherwise Lint will ignore it. Linticator allows you to use variables for these settings. For example, to mark B.cpp and C.h as library, you can use the following flag:
To ignore directories, wildcards in combination with libm and libh can be used:
Configuration Troubleshooting Guide¶
If you were able to complete the configuration wizard but Linticator doesn't seem to work, there are a few things you can check.
First, you can revisit the configuration tester from the initial setup wizard under the Help → Linticator Configuration menu.
Linticator creates a hidden directory .lint your project root where it stores its auto-generated source files. This looks as follows:
If some of these are missing, there might be a problem with the configuration builder. First, check if the builder is active in your project's settings:
Second, check the Linticator Console for entries related to the configuration builder: