BoomMicrophone/nixpkgs-suyu
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

verible: 0.0-2172-g238b6df60 -> 0.0-2472-ga80124e1

Browse source 
Uses bazel_4 now; works well with the recently added testing
capability in buildBazelPackage (#192639)
This commit is contained in:
Henner Zeller 2022-10-21 03:29:23 -07:00
parent 295778ad21
commit c4c025e250
1 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
pkgs/development/tools/verible/default.nix
View file

@ -13,18 +13,18 @@ let
in
buildBazelPackage rec {
pname = "verible";
version = "0.0-2172-g238b6df6";
version = "0.0-2472-ga80124e1";
# These environment variables are read in bazel/build-version.py to create
# a build string. Otherwise it would attempt to extract it from .git/.
GIT_DATE = "2022-08-08";
GIT_DATE = "2022-10-21";
GIT_VERSION = version;
src = fetchFromGitHub {
owner = "chipsalliance";
repo = "verible";
rev = "v${version}";
sha256 = "sha256-iOJhdbipuqqBiYGgk95d1c8bEK6Z16l16GuzYCQRc2g=";
sha256 = "sha256:0jpdxqhnawrl80pbc8544pyggdp5s3cbc7byc423d5v0sri2f96v";
};
patches = [
@ -41,10 +41,13 @@ buildBazelPackage rec {
];
fetchAttrs = {
# Fixed output derivation hash after bazel fetch
# Fixed output derivation hash after bazel fetch.
# This varies per platform, probably from the JDK pulled in being part
# of the output derivation ? Is there a more robust way to do this ?
# (Hashes extracted from the ofborg build logs)
sha256 = {
aarch64-linux = "sha256-BnZ/jZ+KF/sNrVSYu1UGxyBe66fWVaIrwiqRQuYGVrY=";
x86_64-linux = "sha256-45PINJ7VtL5Jl/nAQNkiSCt8wUwtytNfgeNMZaz3Y9U=";
aarch64-linux = "sha256-6Udp7sZKGU8gcy6+5WPhkSWunf1sVkha8l5S1UQsC04=";
x86_64-linux = "sha256-WfhgbJFaM/ipdd1dRjPeVZ1mK2hotb0wLmKjO7e+BO4=";
}.${system} or (throw "No hash for system: ${system}");
};
@ -69,6 +72,7 @@ buildBazelPackage rec {
verilog/tools
'';
bazel = bazel_4;
removeRulesCC = false;
bazelTarget = ":install-binaries";
bazelTestTargets = [ "//..." ];