Hi,
Thanks for all the help and tips everyone provided. I finally have
successfully run the clang analyzer on LibreOffice ~master with
'--with-system-libs'. The only exceptions being:
1.) '--with-system-saxon=no'
Because the open source HE variant of saxon does not have all the
necessary features.
2.) '--with-system-libcmis'
Because I couldnt get LO building with Fedora's libcmis-0.2.3 and
libcmis-devel-0.2.3.
I have uploaded the generated report here:
http://lbalbalba.x90x.net/clang-analyzer/libreoffice-with-system-libs/
Please do note that the C++ *analyzer* (not the compiler) is still
very much regarded as a 'work-in-progress' at this point, so you are
likely to run into false positives. And of course, if you do find a
false positive, you can always consider assisting in improving the
analyzer by submitting a test-case and bug report over here ;)  :
http://clang-analyzer.llvm.org/filing_bugs.html
Have fun!
Regards,
John Smith
PS1: Besides possible 'bugs', the compiler also reported quite a few
compiler 'errors'. But because they all looked like the same error, I
have only uploaded the 1st one due to space considerations.
PS2: I would have loved to mention the exact revision of 'master' I
ran this test on, but Im really new to git. Is there a git command
that can provide a human readable/meaningful revision number, like you
can get with 'svn info' ?
Context
  Re: Static src analysis of LibreOffice · bfo
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.