3
0
Fork 0
forked from mirrors/nixpkgs
nixpkgs/pkgs/development/tools/analysis/include-what-you-use/default.nix
Tobias Geerinckx-Rice ca8903c3c2 include-what-you-use: use unversioned llvm attribute
...in the expression itself, while hard-coding the officially supported
version in all-packages.nix for sanity's sake (mine).
2015-12-20 03:22:24 +01:00

37 lines
1.3 KiB
Nix

{ stdenv, fetchurl, cmake, llvmPackages }:
# Also bump llvmPackages in all-packages.nix to the supported version!
let version = "0.5"; in
stdenv.mkDerivation rec {
name = "include-what-you-use-${version}";
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; {
inherit version;
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 ];
};
}