• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 1081 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

pclint

Mike Newsome

I am having trouble integrating plLint to uVision4. Specifically I cannot stop it complaining about lines in stdio.h, starting with:

extern _ARMABI int remove(const char * /*filename*/) __attribute__((__nonnull__(1)));

I am not clear whether I should be using co-rv.lnt or co-kcarm.lint to handle compiler peculiarities.

Can anyone help please?

Thanks in advance

  • 0

    "I am not clear whether I should be using co-rv.lnt or co-kcarm.lint"

    As a pure guess, it would seem likely that:

    co-rv.lnt - would be for the RealView (ie, ARM) tools;

    co-kcarm.lint - would be for the Keil CARM compiler?

  • 0 in reply to Andy Neil

    Thanks Andy. I have just realised that I didn't add enough (any) information about what I am doing!

    I wish to lint code written for an LPC17xx ARM Cortex-M3 processor, written for uVision4. I know this was once RealView, but thought the kcarm file might be Keil C ARM.

    Can I find what predefined macros are created by the compiler?

    Many thanks again.