blob: 374f0fee3f11050518fd1f0193c30cf7f2bb65b5 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
{ stdenv, fetchurl, cmake, llvmPackages }:
stdenv.mkDerivation rec {
name = "include-what-you-use-${version}";
# Also bump llvmPackages in all-packages.nix to the supported version!
version = "0.5";
src = fetchurl {
sha256 = "19pwhgwvfr86n8ks099p9r02v7zh8d3qs7g7snzkhpdgq1azww85";
url = "${meta.homepage}/downloads/${name}.src.tar.gz";
};
buildInputs = with llvmPackages; [ clang llvm ];
nativeBuildInputs = [ cmake ];
cmakeFlags = [ "-DIWYU_LLVM_ROOT_PATH=${llvmPackages.clang-unwrapped}" ];
enableParallelBuilding = true;
meta = with stdenv.lib; {
description = "Analyze #includes in C/C++ source files with clang";
longDescription = ''
For every symbol (type, function variable, or macro) that you use in
foo.cc, either foo.cc or foo.h should #include a .h file that exports the
declaration of that symbol. The main goal of include-what-you-use is to
remove superfluous #includes, both by figuring out what #includes are not
actually needed for this file (for both .cc and .h files), and by
replacing #includes with forward-declares when possible.
'';
homepage = http://include-what-you-use.org;
license = licenses.bsd3;
platforms = platforms.linux;
maintainers = with maintainers; [ nckx ];
};
}
|