gicho / cppcheclipse

Automatically exported from code.google.com/p/cppcheclipse
0 stars 0 forks source link

File extensions should be configurable, Pro*C Files with ending .pc for example are not checked #46

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Right mouse click on a file with extension .pc and cppcheclipse does not 
check the file
2. cppcheck <filname>.pc will check the file
3. CDT file extensions can be ammended to include *.pc files as C/C++ files

What is the expected output? What do you see instead? Please provide output
of the console view of cppcheclipse as well as the Eclipse error log.

s.a.

What version of the cppcheclipse, cppcheck, Eclipse and Java are you using?

latest versions

On what operating system?

N/A, all

Please provide any additional information below.

Original issue reported on code.google.com by gsteinme...@googlemail.com on 16 May 2012 at 9:56

GoogleCodeExporter commented 8 years ago
The extension pc will never be checked by cppcheck itself. Just compare with 
the file lib/path.cpp Path::acceptFile 
(https://github.com/danmar/cppcheck/blob/master/lib/path.cpp#L209). Only the 
extension listed there are supported, i.e.
cpp, cxx, cc, c++, tpp, txx, c. Please open an enhancement request at cppcheck 
first (http://sourceforge.net/apps/trac/cppcheck/timeline) and link it here, if 
you want to have support for the extension pc as well.

Original comment by konra...@gmx.de on 16 Jul 2012 at 7:03

GoogleCodeExporter commented 8 years ago
I know this has been closed as invalid but I believe that this is a defect.
cppcheck correctly analyses .pc (Pro*C) files out of the box via the command 
line or via its GUI. 
I can see that it is not listed in the extension list, a copy of the cppcheck 
source was downloaded and this file extension was added to the list and 
cppcheck was recompiled, the new cppcheck executable ran as expected outside of 
eclipse on .cpp , .c and .pc files. When returning to eclispe and pointing the 
plugin to the newly compiled executable it still did not analyse .pc files.

Original comment by priy...@gmail.com on 21 Oct 2014 at 12:36