[splint-discuss] Is this a splint problem, a Cygwin problem,
or a stupidity problem?
Michael.Wojcik at MicroFocus.com
Fri May 19 14:25:22 EDT 2006
> From: splint-discuss-bounces at cs.virginia.edu
> [mailto:splint-discuss-bounces at cs.virginia.edu] On Behalf Of
> Philip Goetz
> Sent: Friday, 19 May, 2006 13:05
> Hi - I'm trying to get splint to work under Cygwin.
Disclaimer: I've never tried to run splint under cygwin; I just use the
native Win32 build. (I have MS Services for Unix installed, and cygwin
would conflict with them.)
> My problem is that I can't get it to read any of the paths I give it.
> This is how I try to set the paths in my .bashrc:
> alias splint="splint -I/usr/include/c++/3.3.3:usr/local/include"
Have you tried:
alias splint="splint -I/usr/include/c++/3.3.3 -I/usr/local/include"
I've never seen -I used to pass a path list, only the pathname of a
directory, as is customary for C compilers; and I don't see anything in
the splint documentation that would lead me to expect it to work.
> # LARCH_PATH is for splint
> export SPLINT=/cygdrive/c/lang/C/splint-126.96.36.199
Is this actually a cygwin build of splint? You use a cygwin path here,
but in the splint error messages you show below, it appears to have been
translated to a conventional Windows path. Something's not right there.
> $ !splint
> splint main.cpp
> Splint 188.8.131.52 --- 11 Feb 2002
> Command Line: Unrecognized file extension:
> main.cpp (assuming .cpp is C source code)
I don't think you're going to have much luck running splint against C++
source anyway. It's a C analyzer.
Principal Software Systems Developer, Micro Focus
More information about the splint-discuss