On Tue, Aug 7, 2012 at 10:47 AM, Lubos Lunak <l.lunak@suse.cz> wrote:
It doesn't make much sense to analyze with Clang but compile with GCC.
The idea here is that you can use your existing build setup 'as-is'
without being forced to change your build setup like your compiler,
Makefiles, etc. And still be able to analyze your codebase, without
having to make any other changes.
Configure detects various features of the compiler and if you actually use
GCC, certain things will not be set up properly for Clang. Use Clang for
compiling too.
Alright, I'll do that the next time I run the analyzer.
- John
Context
- Re: Static src analysis of LibreOffice (continued)
Re: Static src analysis of LibreOffice · Terrence Enger
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.