Skip to content

Commit

Permalink
Prepare release 0.1.1
Browse files Browse the repository at this point in the history
  • Loading branch information
ThetaSinner committed Jul 18, 2024
1 parent a7f9a2d commit 42717e5
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 20 deletions.
2 changes: 1 addition & 1 deletion checked_cli/Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion checked_cli/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "checked_cli"
version = "0.1.0"
version = "0.1.1"
edition = "2021"

[[bin]]
Expand Down
18 changes: 0 additions & 18 deletions flake.nix
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,6 @@
, ...
}:
let
opensslStatic =
if system == "x86_64-darwin"
then pkgs.openssl
else pkgs.pkgsStatic.openssl;

craneLib = crane.lib.${system};
src = craneLib.cleanCargoSource (craneLib.path ./checked_cli);

Expand Down Expand Up @@ -112,22 +107,9 @@
]) ++ (with pkgs; [
nodejs_20
minisign
libsodium
upx # For binary size optimisation. Not currently working with `checked_cli`, try again later
binaryen # For wasm-opt, optimising wasms before packaging
]);

shellHook = ''
# This is enough to get libsodium-sys-stable to link against the libsodium we're providing
export SODIUM_LIB_DIR="${pkgs.libsodium}/lib/"
export SODIUM_SHARED="1"
# Irritatingly, the above isn't enough. Because `lair_keystore` depends on `lair_keystore_api` in its `build.rs`
# which apparently doesn't go through the same build process. That's probably enough justification that it should
# not have that dependency but for now, we get around the problem by configuring the linker directly, outside Cargo's
# build process...
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SODIUM_LIB_DIR
'';
};
};
};
Expand Down

0 comments on commit 42717e5

Please sign in to comment.