OCLint 0.8 Release Candidate Testing

[Longyi Qi]

Kudos to the LLVM community, and now LLVM 3.4 is released. We then have the OCLint 0.8 release candidate ready for your testing.

With great work from Joris, OCLint has been ported to MinGW environment on Windows platform, so we would like to ship a binary for MinGW users, in addition to OS X* build and Linux build.

- Windows 7 + MinGW 4.7.1 64bit: http://archives.oclint.org/releases/0.8rc/oclint-0.8rc1-amd64-windows-7.zip

- OS X 10.9 64bit: http://archives.oclint.org/releases/0.8rc/oclint-0.8rc1-x86_64-darwin-13.0.0.tar.gz

- Ubuntu 12.04 LTS 64bit: http://archives.oclint.org/releases/0.8rc/oclint-0.8rc1-x86_64-linux-3.2.0-32-generic.tar.gz

All sorts of feedback are sincerely appreciated. And we thank you for all your contributions to this release, especially to our hard-working contributors. We hope to learn from your feedback, and provide the GA builds for you very soon.

Regards,

Longyi

* Mac OS X 10.6 is no longer supported from us due to its lack of default libc++ library. However, people who has manually set up libc++ on the machine can continue using the tool by building OCLint locally.

[Longyi Qi]

Thanks for sharing this with us. Static code analysis is a broad concept. ClangFormat is more like a syntactic analysis/formatting tool, and OCLint, in addition to analyze syntax, inspects on the intermediate representations of the source code for better understanding of the source code and better accuracy. I believe developers can leverage two tools to tackle different angles of code quality issues.

On Jan 8, 2014, at 10:35 AM, fly2never <fly2...@gmail.com> wrote:

Hello, I've found ClangFormat, have fun with it!

--
You received this message because you are subscribed to the Google Groups "OCLint Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to oclint-users...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Longyi Qi]

This is an interesting situation. 0.8 release doesn't ship with FeatureEnvy, but your build tries to use it. Could you try delete existing installation completely (especially the ../lib/oclint/rules  folder), and install it from scratch? I am thinking you have installed this rc build by overriding an existing installation, which originally contains a libFeatureEnvyRule.dylib file. 

Let me know if it fixes, thanks!

Longyi

On Thu, Jan 9, 2014 at 8:56 AM, Jani Jegoroff <jani.j...@gmail.com> wrote:

I did a test run with release candidate and got a following error:

** BUILD SUCCEEDED **

(5 commands with analyzer issues)
scan-build: 5 bugs found.
scan-build: Run 'scan-view /Users/<jenkins-job-path>/workspace/clangScanBuildReports/2014-01-09-1' to examine bug reports.
dyld: lazy symbol binding failed: Symbol not found: __ZNK5clang15ast_type_traits11ASTNodeKind8isBaseOfES1_Pj
  Referenced from: /usr/local/bin/../lib/oclint/rules/libFeatureEnvyRule.dylib
  Expected in: flat namespace

dyld: Symbol not found: __ZNK5clang15ast_type_traits11ASTNodeKind8isBaseOfES1_Pj
  Referenced from: /usr/local/bin/../lib/oclint/rules/libFeatureEnvyRule.dylib
  Expected in: flat namespace

[PMD] Collecting PMD analysis files...
[PMD] Finding all files that match the pattern **/oclint.xml
[WARNINGS] Parsing warnings in console log with parser Clang (LLVM based)
Archiving artifacts
Publishing Clang scan-build results
Finished: SUCCESS

[Joris Dauphin]

Some feed backs:

The windows version seems to works ^^

Some remarks:

- oclint --version doesn't give the *oclint* version (it just give LLVM version)

- I think it should be better to ship with LLVM 3.4 (oclint --version tell it is compiled with LLVM3.4svn )

- LICENSE copyright is 2013, it may be 2014

- When does "lib\clang\3.4\include\*" used ?