2021-01-22 11:25:31 +00:00
|
|
|
{ lowPrio, newScope, pkgs, lib, stdenv, cmake, gccForLibs
|
2020-01-12 20:22:29 +00:00
|
|
|
, libxml2, python3, isl, fetchurl, overrideCC, wrapCCWith
|
2018-05-23 16:39:07 +00:00
|
|
|
, buildLlvmTools # tools, but from the previous stage, for cross
|
|
|
|
, targetLlvmLibraries # libraries, but from the next stage, for cross
|
2017-09-16 00:38:38 +00:00
|
|
|
}:
|
|
|
|
|
|
|
|
let
|
2018-05-04 15:54:06 +00:00
|
|
|
release_version = "5.0.2";
|
2017-09-16 00:38:38 +00:00
|
|
|
version = release_version; # differentiating these is important for rc's
|
2020-04-07 00:46:15 +00:00
|
|
|
targetConfig = stdenv.targetPlatform.config;
|
2017-09-16 00:38:38 +00:00
|
|
|
|
|
|
|
fetch = name: sha256: fetchurl {
|
2018-09-19 13:02:21 +00:00
|
|
|
url = "https://releases.llvm.org/${release_version}/${name}-${version}.src.tar.xz";
|
2017-09-16 00:38:38 +00:00
|
|
|
inherit sha256;
|
|
|
|
};
|
|
|
|
|
2018-05-04 15:54:06 +00:00
|
|
|
clang-tools-extra_src = fetch "clang-tools-extra" "018b3fiwah8f8br5i26qmzh6sjvzchpn358sn8v079m49f2jldm3";
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
llvm_meta = {
|
|
|
|
license = lib.licenses.ncsa;
|
|
|
|
maintainers = with lib.maintainers; [ lovek323 raskin dtzWill primeos ];
|
|
|
|
platforms = lib.platforms.all;
|
|
|
|
};
|
|
|
|
|
2021-01-22 11:25:31 +00:00
|
|
|
tools = lib.makeExtensible (tools: let
|
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 08:23:57 +00:00
|
|
|
callPackage = newScope (tools // { inherit stdenv cmake libxml2 python3 isl release_version version fetch buildLlvmTools; });
|
2018-06-14 14:22:33 +00:00
|
|
|
mkExtraBuildCommands = cc: ''
|
|
|
|
rsrc="$out/resource-root"
|
|
|
|
mkdir "$rsrc"
|
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 08:23:57 +00:00
|
|
|
ln -s "${cc.lib}/lib/clang/${release_version}/include" "$rsrc"
|
2018-06-14 14:22:33 +00:00
|
|
|
echo "-resource-dir=$rsrc" >> $out/nix-support/cc-cflags
|
2021-05-11 21:12:04 +00:00
|
|
|
ln -s "${targetLlvmLibraries.compiler-rt.out}/lib" "$rsrc/lib"
|
2018-06-14 14:22:33 +00: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 08:23:57 +00:00
|
|
|
|
2018-05-23 16:39:07 +00:00
|
|
|
in {
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
libllvm = callPackage ./llvm {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
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 08:23:57 +00:00
|
|
|
|
2021-05-11 08:35:41 +00:00
|
|
|
# `llvm` historically had the binaries. When choosing an output explicitly,
|
2021-10-15 14:30:58 +00:00
|
|
|
# we need to reintroduce `outputSpecified` to get the expected behavior e.g. of lib.get*
|
|
|
|
llvm = tools.libllvm.out // { outputSpecified = 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 08:23:57 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
libllvm-polly = callPackage ./llvm {
|
|
|
|
inherit llvm_meta;
|
|
|
|
enablePolly = true;
|
|
|
|
};
|
2018-06-14 14:22:33 +00:00
|
|
|
|
2021-10-15 14:30:58 +00:00
|
|
|
llvm-polly = tools.libllvm-polly.lib // { outputSpecified = 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 08:23:57 +00:00
|
|
|
|
|
|
|
libclang = callPackage ./clang {
|
2021-05-11 21:12:04 +00:00
|
|
|
inherit clang-tools-extra_src llvm_meta;
|
2018-07-27 19:52:50 +00:00
|
|
|
};
|
|
|
|
|
2021-10-15 14:30:58 +00:00
|
|
|
clang-unwrapped = tools.libclang.out // { outputSpecified = 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 08:23:57 +00:00
|
|
|
|
|
|
|
llvm-manpages = lowPrio (tools.libllvm.override {
|
2018-07-27 19:52:50 +00:00
|
|
|
enableManpages = true;
|
2020-01-12 20:22:29 +00:00
|
|
|
python3 = pkgs.python3; # don't use python-boot
|
2018-07-27 19:52:50 +00: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 08:23:57 +00:00
|
|
|
clang-manpages = lowPrio (tools.libclang.override {
|
2018-07-27 19:52:50 +00:00
|
|
|
enableManpages = true;
|
2020-01-12 20:22:29 +00:00
|
|
|
python3 = pkgs.python3; # don't use python-boot
|
2018-05-23 16:39:07 +00:00
|
|
|
});
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2022-01-07 01:30:01 +00:00
|
|
|
# pick clang appropriate for package set we are targeting
|
|
|
|
clang =
|
2022-01-07 11:58:21 +00:00
|
|
|
/**/ if stdenv.targetPlatform.useLLVM or false then tools.clangUseLLVM
|
|
|
|
else if (pkgs.targetPackages.stdenv or stdenv).cc.isGNU then tools.libstdcxxClang
|
2022-01-07 01:30:01 +00:00
|
|
|
else tools.libcxxClang;
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2018-06-14 14:22:33 +00:00
|
|
|
libstdcxxClang = wrapCCWith rec {
|
2018-05-23 16:39:07 +00:00
|
|
|
cc = tools.clang-unwrapped;
|
2020-06-17 20:33:56 +00:00
|
|
|
# libstdcxx is taken from gcc in an ad-hoc way in cc-wrapper.
|
|
|
|
libcxx = null;
|
2020-03-18 15:28:52 +00:00
|
|
|
extraPackages = [
|
2018-06-14 14:22:33 +00:00
|
|
|
targetLlvmLibraries.compiler-rt
|
|
|
|
];
|
2020-04-14 00:44:43 +00:00
|
|
|
extraBuildCommands = mkExtraBuildCommands cc;
|
2017-09-16 00:38:38 +00:00
|
|
|
};
|
|
|
|
|
2018-06-14 14:22:33 +00:00
|
|
|
libcxxClang = wrapCCWith rec {
|
2018-05-23 16:39:07 +00:00
|
|
|
cc = tools.clang-unwrapped;
|
2019-01-26 15:17:57 +00:00
|
|
|
libcxx = targetLlvmLibraries.libcxx;
|
2018-06-14 14:22:33 +00:00
|
|
|
extraPackages = [
|
|
|
|
targetLlvmLibraries.libcxxabi
|
|
|
|
targetLlvmLibraries.compiler-rt
|
|
|
|
];
|
|
|
|
extraBuildCommands = mkExtraBuildCommands cc;
|
2017-09-16 00:38:38 +00:00
|
|
|
};
|
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
lld = callPackage ./lld {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
lldb = callPackage ./lldb {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
2018-06-14 14:22:33 +00:00
|
|
|
});
|
2018-05-23 16:39:07 +00:00
|
|
|
|
2021-01-22 11:25:31 +00:00
|
|
|
libraries = lib.makeExtensible (libraries: let
|
2020-01-12 20:22:29 +00:00
|
|
|
callPackage = newScope (libraries // buildLlvmTools // { inherit stdenv cmake libxml2 python3 isl release_version version fetch; });
|
2018-05-23 16:39:07 +00:00
|
|
|
in {
|
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
compiler-rt = callPackage ./compiler-rt {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
2018-06-14 14:22:33 +00:00
|
|
|
|
2018-05-23 16:39:07 +00:00
|
|
|
stdenv = overrideCC stdenv buildLlvmTools.clang;
|
|
|
|
|
|
|
|
libcxxStdenv = overrideCC stdenv buildLlvmTools.libcxxClang;
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
libcxx = callPackage ./libcxx {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
libcxxabi = callPackage ./libcxxabi {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-05-11 21:12:04 +00:00
|
|
|
openmp = callPackage ./openmp {
|
|
|
|
inherit llvm_meta;
|
|
|
|
};
|
2018-06-14 14:22:33 +00:00
|
|
|
});
|
2017-09-16 00:38:38 +00:00
|
|
|
|
2021-08-07 07:42:33 +00:00
|
|
|
in { inherit tools libraries release_version; } // libraries // tools
|