I usually suggest avoiding doing the lint pass as an adjunct to the compile unless there is some very compelling reason 
to do so.  Usually the effect that is desired by the developer is ensuring that the lint check occurs whenever the 
source changes, "just like for the object file".  The downside in this case is that full dependency checking isn't done 
by default by the QNX build system anyway, so you're probably not linting as thoroughly as you might ideally like.  If 
your static analysis tool(s) generate some sort of output file - even just redirected stdout - you can easily set up 
your own rules independent of (most of) the internal guts of the build system.

CCPOST is intended for "C Compilation Post-Processing" and is simply expanded at the end of the compiler command line.  
This could be leveraged something along the lines of:

    CCPOST = && $(do-lint) $<

to run a lint check for each successful compile.

I've attached the makefile which we use internally for linting.  There's probably way more stuff in there than you'll 
need, but hopefully it'll give you some ideas.

[The usual disclaimers apply: this is unsupported software; no warranty; trademarks belong to their registered holders; 
no endorsement by QNX of any third party should be inferred; yada yada.]