2021-05-18 16:15:03 +02:00
|
|
|
{ lib, stdenv, llvm_meta, fetch, substituteAll, cmake, libxml2, libllvm, version, clang-tools-extra_src, python3
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
, buildLlvmTools
|
2019-02-28 19:01:31 +01:00
|
|
|
, fixDarwinDylibNames
|
|
|
|
, enableManpages ? false
|
|
|
|
, enablePolly ? false # TODO: get this info from llvm (passthru?)
|
|
|
|
}:
|
|
|
|
|
|
|
|
let
|
|
|
|
self = stdenv.mkDerivation ({
|
2019-08-16 15:57:51 +02:00
|
|
|
pname = "clang";
|
2019-06-24 02:49:25 +02:00
|
|
|
inherit version;
|
2019-02-28 19:01:31 +01:00
|
|
|
|
2019-08-06 01:32:16 +02:00
|
|
|
src = fetch "cfe" "0ihnbdl058gvl2wdy45p5am55bq8ifx8m9mhcsgj9ax8yxlzvvvh";
|
2019-07-12 02:09:55 +02:00
|
|
|
|
2019-02-28 19:01:31 +01:00
|
|
|
unpackPhase = ''
|
2019-07-12 02:09:55 +02:00
|
|
|
unpackFile $src
|
2019-02-28 19:01:31 +01:00
|
|
|
mv cfe-${version}* clang
|
|
|
|
sourceRoot=$PWD/clang
|
|
|
|
unpackFile ${clang-tools-extra_src}
|
|
|
|
mv clang-tools-extra-* $sourceRoot/tools/extra
|
|
|
|
'';
|
|
|
|
|
2020-01-12 21:22:29 +01:00
|
|
|
nativeBuildInputs = [ cmake python3 ]
|
2021-01-22 12:25:31 +01:00
|
|
|
++ lib.optional enableManpages python3.pkgs.sphinx
|
|
|
|
++ lib.optional stdenv.hostPlatform.isDarwin fixDarwinDylibNames;
|
2019-02-28 19:01:31 +01:00
|
|
|
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
buildInputs = [ libxml2 libllvm ];
|
2019-02-28 19:01:31 +01:00
|
|
|
|
|
|
|
cmakeFlags = [
|
|
|
|
"-DCMAKE_CXX_FLAGS=-std=c++11"
|
2019-04-11 04:42:01 +02:00
|
|
|
"-DCLANGD_BUILD_XPC=OFF"
|
2020-06-27 20:27:50 +02:00
|
|
|
"-DLLVM_ENABLE_RTTI=ON"
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
"-DLLVM_CONFIG_PATH=${libllvm.dev}/bin/llvm-config${lib.optionalString (stdenv.hostPlatform != stdenv.buildPlatform) "-native"}"
|
2021-01-22 12:25:31 +01:00
|
|
|
] ++ lib.optionals enableManpages [
|
2019-02-28 19:01:31 +01:00
|
|
|
"-DCLANG_INCLUDE_DOCS=ON"
|
|
|
|
"-DLLVM_ENABLE_SPHINX=ON"
|
|
|
|
"-DSPHINX_OUTPUT_MAN=ON"
|
|
|
|
"-DSPHINX_OUTPUT_HTML=OFF"
|
|
|
|
"-DSPHINX_WARNINGS_AS_ERRORS=OFF"
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
] ++ lib.optionals (stdenv.hostPlatform != stdenv.buildPlatform) [
|
|
|
|
"-DLLVM_TABLEGEN_EXE=${buildLlvmTools.llvm}/bin/llvm-tblgen"
|
|
|
|
"-DCLANG_TABLEGEN=${buildLlvmTools.libclang.dev}/bin/clang-tblgen"
|
2021-01-22 12:25:31 +01:00
|
|
|
] ++ lib.optionals enablePolly [
|
2019-02-28 19:01:31 +01:00
|
|
|
"-DWITH_POLLY=ON"
|
|
|
|
"-DLINK_POLLY_INTO_TOOLS=ON"
|
|
|
|
];
|
|
|
|
|
2019-04-11 04:42:01 +02:00
|
|
|
patches = [
|
|
|
|
./purity.patch
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
./xpc.patch
|
2019-04-12 04:52:30 +02:00
|
|
|
# Backport for -static-pie, which the latter touches, and which is nice in
|
|
|
|
# its own right.
|
|
|
|
./static-pie.patch
|
2019-05-10 11:29:09 +02:00
|
|
|
# Backport for the `--unwindlib=[libgcc|compiler-rt]` flag, which is
|
2019-04-12 04:52:30 +02:00
|
|
|
# needed for our bootstrapping to not interfere with C.
|
|
|
|
./unwindlib.patch
|
2019-07-27 22:15:58 +02:00
|
|
|
# https://reviews.llvm.org/D51899
|
|
|
|
./compiler-rt-baremetal.patch
|
2020-01-28 17:35:19 +01:00
|
|
|
# make clang -xhip use $PATH to find executables
|
|
|
|
./HIP-use-PATH-8.patch
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
./gnu-install-dirs.patch
|
2021-05-18 16:15:03 +02:00
|
|
|
(substituteAll {
|
|
|
|
src = ../../clang-6-10-LLVMgold-path.patch;
|
|
|
|
libllvmLibdir = "${libllvm.lib}/lib";
|
|
|
|
})
|
2019-04-11 04:42:01 +02:00
|
|
|
];
|
2019-02-28 19:01:31 +01:00
|
|
|
|
|
|
|
postPatch = ''
|
|
|
|
sed -i -e 's/DriverArgs.hasArg(options::OPT_nostdlibinc)/true/' \
|
|
|
|
-e 's/Args.hasArg(options::OPT_nostdlibinc)/true/' \
|
|
|
|
lib/Driver/ToolChains/*.cpp
|
|
|
|
|
|
|
|
# Patch for standalone doc building
|
|
|
|
sed -i '1s,^,find_package(Sphinx REQUIRED)\n,' docs/CMakeLists.txt
|
2021-01-22 12:25:31 +01:00
|
|
|
'' + lib.optionalString stdenv.hostPlatform.isMusl ''
|
2019-02-28 19:01:31 +01:00
|
|
|
sed -i -e 's/lgcc_s/lgcc_eh/' lib/Driver/ToolChains/*.cpp
|
2021-01-22 12:25:31 +01:00
|
|
|
'' + lib.optionalString stdenv.hostPlatform.isDarwin ''
|
2019-02-28 19:01:31 +01:00
|
|
|
substituteInPlace tools/extra/clangd/CMakeLists.txt \
|
|
|
|
--replace "NOT HAVE_CXX_ATOMICS64_WITHOUT_LIB" FALSE
|
|
|
|
'';
|
|
|
|
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
outputs = [ "out" "lib" "dev" "python" ];
|
2019-02-28 19:01:31 +01:00
|
|
|
|
|
|
|
postInstall = ''
|
|
|
|
ln -sv $out/bin/clang $out/bin/cpp
|
|
|
|
|
|
|
|
# Move libclang to 'lib' output
|
|
|
|
moveToOutput "lib/libclang.*" "$lib"
|
|
|
|
substituteInPlace $out/lib/cmake/clang/ClangTargets-release.cmake \
|
|
|
|
--replace "\''${_IMPORT_PREFIX}/lib/libclang." "$lib/lib/libclang."
|
|
|
|
|
|
|
|
mkdir -p $python/bin $python/share/clang/
|
|
|
|
mv $out/bin/{git-clang-format,scan-view} $python/bin
|
|
|
|
if [ -e $out/bin/set-xcode-analyzer ]; then
|
|
|
|
mv $out/bin/set-xcode-analyzer $python/bin
|
|
|
|
fi
|
|
|
|
mv $out/share/clang/*.py $python/share/clang
|
|
|
|
rm $out/bin/c-index-test
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
|
|
|
|
mkdir -p $dev/bin
|
|
|
|
cp bin/clang-tblgen $dev/bin
|
2019-02-28 19:01:31 +01:00
|
|
|
'';
|
|
|
|
|
|
|
|
passthru = {
|
|
|
|
isClang = true;
|
llvmPackages: Multuple outputs for everythting
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
2020-10-15 10:23:57 +02:00
|
|
|
inherit libllvm;
|
2019-02-28 19:01:31 +01:00
|
|
|
};
|
|
|
|
|
2021-05-11 23:12:04 +02:00
|
|
|
meta = llvm_meta // {
|
|
|
|
homepage = "https://clang.llvm.org/";
|
|
|
|
description = "A C language family frontend for LLVM";
|
|
|
|
longDescription = ''
|
|
|
|
The Clang project provides a language front-end and tooling
|
|
|
|
infrastructure for languages in the C language family (C, C++, Objective
|
|
|
|
C/C++, OpenCL, CUDA, and RenderScript) for the LLVM project.
|
|
|
|
It aims to deliver amazingly fast compiles, extremely useful error and
|
|
|
|
warning messages and to provide a platform for building great source
|
|
|
|
level tools. The Clang Static Analyzer and clang-tidy are tools that
|
|
|
|
automatically find bugs in your code, and are great examples of the sort
|
|
|
|
of tools that can be built using the Clang frontend as a library to
|
|
|
|
parse C/C++ code.
|
|
|
|
'';
|
2019-02-28 19:01:31 +01:00
|
|
|
};
|
2021-01-22 12:25:31 +01:00
|
|
|
} // lib.optionalAttrs enableManpages {
|
2019-08-14 16:07:30 +02:00
|
|
|
pname = "clang-manpages";
|
2019-02-28 19:01:31 +01:00
|
|
|
|
|
|
|
buildPhase = ''
|
|
|
|
make docs-clang-man
|
|
|
|
'';
|
|
|
|
|
|
|
|
installPhase = ''
|
|
|
|
mkdir -p $out/share/man/man1
|
|
|
|
# Manually install clang manpage
|
|
|
|
cp docs/man/*.1 $out/share/man/man1/
|
|
|
|
'';
|
|
|
|
|
|
|
|
outputs = [ "out" ];
|
|
|
|
|
|
|
|
doCheck = false;
|
|
|
|
|
2021-05-11 23:12:04 +02:00
|
|
|
meta = llvm_meta // {
|
|
|
|
description = "man page for Clang ${version}";
|
|
|
|
};
|
2019-02-28 19:01:31 +01:00
|
|
|
});
|
|
|
|
in self
|