This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Using PC-lint 9 with CCSv4/v5

Other Parts Discussed in Thread: MSP430G2252

I want to use PC-lint 9 with my CCSv4 (and v5 in a short period). During the PC-lint setup, I have to choose the compiler which my IDE is using. So what compiler is CCSv4 using for my MSP430 projects?

 

Are there any other hints when using PC-lint 9 with CCS?

  • CCS is using the Texas Instruments MSP430 compiler.

  • There was another company  that was doing some PC Lint integration with Eclipse (which CCS is based on) that might be worth a look.

     

    http://www.riverblade.co.uk/products/visual_lint/index.html

  • Well, I don't think that I want to pay money for such an apparently easy task. There should be a way to accomplish this on my own.

  • JohnS said:

    CCS is using the Texas Instruments MSP430 compiler.

    I have a personal copy of PC-Lint 8.* and I could not tailor the tool to be used with CCSv4, even running by command line, the header files from TI produce a lot of warnings/errors.
    Can someone post the configuration files for PC lint?

  • I use the following setup of Lint (version 9.00h) with CCSv4:

    - all source code files are listed in a file called files.lnt, one per line
    - Lint is called with c:\lint\lint-nt.exe -i"C:\work\workspace4_new\Lueftersteuerung\include" -d__MSP430G2252__ -e830 -e773 files.lnt > lintoutput.txt

    This suppresses two info messages (830 and 773) and mitigates the problem. Calling Lint with the option -w1 also helps, because then only errors are shown.

    But currently I'm searching for a solution to tell Lint it should ignore a specific file set. When I get a nice working solution, I will post it here. This might do the trick: http://www.gimpel.com/html/techfaq.htm#q2

    Ok, I just learned that Lint considers includes in angle brackets and includes supplied by the -i command line option als 'library headers' (+libclass(angle,foreign) is active as a default setting, according to the supplied pdf manual by Lint). We can set the warning levels of these library headers with the option -wlib(#). Now my Lint call looks like so:

    C:\work\workspace4_new\Lueftersteuerung>c:\lint\lint-nt.exe -i"C:\work\workspace4_new\Lueftersteuerung\include" -d__MSP430G2252__ -wlib(2) files.lnt

    This is from the manual PDF:

    -wlib(0)
    No library messages
    -wlib(1)
    Error messages only (when processing library code.)
    -wlib(2)
    Errors and Warnings only
    -wlib(3)
    Error, Warning and Informational. This is the default
    -wlib(4)
    All messages (not otherwise inhibited).
    
    
    With this call, most of the info messages caused by TI's headers are not shown.