blob: 8ba381bc5443f93e68321e63b9f93a5a2a5d6037 (
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
36
37
|
{ lib, stdenv, fetchurl, cmake, llvmPackages, python3 }:
stdenv.mkDerivation rec {
pname = "include-what-you-use";
# Also bump llvmPackages in all-packages.nix to the supported version!
version = "0.16";
src = fetchurl {
sha256 = "sha256-jW/JslU0O8Hl7EWeOVEt8dUcYOA1YpheAHYDYRn/Whw=";
url = "${meta.homepage}/downloads/${pname}-${version}.src.tar.gz";
};
nativeBuildInputs = with llvmPackages; [ cmake llvm.dev llvm python3];
buildInputs = with llvmPackages; [ libclang clang-unwrapped ];
cmakeFlags = [ "-DIWYU_LLVM_ROOT_PATH=${llvmPackages.clang-unwrapped}" ];
postInstall = ''
substituteInPlace $out/bin/iwyu_tool.py \
--replace "'include-what-you-use'" "'$out/bin/include-what-you-use'"
'';
meta = with 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 = "https://include-what-you-use.org";
license = licenses.bsd3;
platforms = platforms.unix;
};
}
|