[cfe-dev] installation of scripts
Alexander Droste via cfe-dev
cfe-dev at lists.llvm.org
Sat Sep 24 05:20:15 PDT 2016
Ah, I thought it had been completed when
https://reviews.llvm.org/D9600 was committed.
Thanks for giving an overview about the state.
I've been using the scripts since the commit
on a dozen of projects and didn't experience any
But I would like to point out one thing:
Using 'intercept-build' and then 'analyze-build'
seems to act a little different than only using
'scan-build' when it comes to wrapper compilers.
'intercept-build + analyze-build' works in case of
using an MPI wrapper compiler, whereas 'scan-build'
never emits any reports.
(1) The shared library is made of a single file, right (ear.c)?
(2) Regarding the tests, the compilation databases
sometimes denote 'g++' as the used compiler.
This seems suspicious. Shouldn't this be 'cc'?
On 24.09.16 03:24, Anna Zaks wrote:
> + Laszlo
> The scan-build-py script is currently under development. The main remaining pieces are:
> (1) Build the library interposition shared libraries as part of the normal clang build process with CMake. This will make sure the library is built with the same compiler that builds clang.
> (2) Integrate scan-build-py's unit and functional tests into clang’s lit-based test suite so they can be run on the bots. Without this we can't qualify scan-build-py as part of clang 4.x releases.
> (3) Dogfood and fix bugs if any.
> (4) Actually add the script installation code.
> Are you using the script?
>> On Sep 13, 2016, at 5:22 AM, Alexander Droste via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>> I'd like to know why some scripts like 'run-clang-tidy.py' get installed
>> into a separate folder (/usr/local/share/clang instead of /usr/local/bin on
>> OSX) and why the scan-build Python package, including intercept-build and
>> analyze-build, is not part of the installation at all. Is there an option
>> to choose the Python scan-build version?
>> cfe-dev mailing list
>> cfe-dev at lists.llvm.org
More information about the cfe-dev