alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity
nixpkgs/pkgs/development/tools/rq/default.nix

38 lines
1.1 KiB
Nix
Raw Normal View History

rq: fix build on darwin
2020-06-05 10:08:28 +01:00
{ stdenv, lib, fetchFromGitHub, rustPlatform, libiconv, llvmPackages, v8 }:
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
rq: 0.10.4 -> 1.0.2
2020-01-08 14:01:08 +00:00
rustPlatform.buildRustPackage rec {
treewide: name -> pname (#67513)
2019-08-31 12:41:23 +01:00
pname = "rq";
rq: 0.10.4 -> 1.0.2
2020-01-08 14:01:08 +00:00
version = "1.0.2";
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
src = fetchFromGitHub {
owner = "dflemstr";
rq: 0.10.4 -> 1.0.2
2020-01-08 14:01:08 +00:00
repo = pname;
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
rev = "v${version}";
rq: 0.10.4 -> 1.0.2
2020-01-08 14:01:08 +00:00
sha256 = "0km9d751jr6c5qy4af6ks7nv3xfn13iqi03wq59a1c73rnf0zinp";
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
};
treewide: fix cargoSha256/cargoHash Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes #121994.
2021-05-07 12:00:49 +01:00
cargoSha256 = "0071q08f75qrxdkbx1b9phqpbj15r79jbh391y32acifi7hr35hj";
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +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 09:23:57 +01:00
buildInputs = [ llvmPackages.libclang v8 ]
rq: fix build on darwin
2020-06-05 10:08:28 +01:00
++ lib.optionals stdenv.isDarwin [ libiconv ];
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
rq: remove #[deny(warnings)] to reduce chance of build failures with rustc update This fixes a build failure due to an added warning.
2021-05-02 21:30:41 +01:00
postPatch = ''
# Remove #[deny(warnings)] which is equivalent to -Werror in C.
# Prevents build failures when upgrading rustc, which may give more warnings.
substituteInPlace src/lib.rs \
--replace "#![deny(warnings)]" ""
'';
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
configurePhase = ''
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 09:23:57 +01:00
export LIBCLANG_PATH="${llvmPackages.libclang.lib}/lib"
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
export V8_SOURCE="${v8}"
'';
rq: 0.10.4 -> 1.0.2
2020-01-08 14:01:08 +00:00
meta = with lib; {
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
description = "A tool for doing record analysis and transformation";
rq: 0.10.4 -> 1.0.2
2020-01-08 14:01:08 +00:00
homepage = "https://github.com/dflemstr/rq";
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
license = with licenses; [ asl20 ];
maintainers: rename filalex77 -> Br1ght0ne
2020-11-17 11:02:06 +00:00
maintainers = with maintainers; [ aristid Br1ght0ne ];
rq: init at 0.9.2 (broken because our v8 is too old, and I'm too weak to update v8)
2016-12-03 22:36:48 +00:00
};
}
Copy permalink