Commit Graph

6 Commits

Author SHA1 Message Date
Jakub Sokołowski cd70fbc912
chore(nix): refactor, fix library packages
Bit of a cleanup to make it more readable and also fix building of libraries.

Moving the actual build to `default.nix` makes `flake.nix` more readable.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-07-30 15:55:08 +02:00
Jakub Sokołowski 75a2aee295
chore: upgrade CI from Nix 2.14 to 2.19
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-13 23:01:13 +01:00
Jakub Sokołowski d8d67d8eb5
chore: update Nix version label for Jenkins CI (#936)
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-11-29 17:16:22 -04:00
richΛrd 164c92554b
refactor: c-bindings 2023-08-10 09:30:38 -04:00
Jakub Sokołowski 14a6f45be4
ci: use Nix dev shell from flake for CI builds
Provides a more predicable build environment for CI.

Depends on: https://github.com/status-im/status-jenkins-lib/pull/60

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-04-04 16:36:30 +02:00
Jakub Sokołowski 349e22bbe8
nix: add Nix flake to build node and library
This way we can build node or the library locally using:
```sh
nix build
nix build .#node
nix build .#library
```
Or just start a shell with Go `1.19.x` using:
```
nix develop
```
Which simply has the same environment as the build shell for the node.

One known snag is that there is currently no simple way to keep `vendorSha256`
updated to match the contents of `go.mod` and `go.sum`. For more details see:
https://discourse.nixos.org/t/how-should-i-build-a-go-package-from-local-source/19490/8

One way around this would be to have our own `vendor` folder, but that's
also a pretty ugly solution that requires manual updating.

Resolves:
https://github.com/waku-org/go-waku/issues/256

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-03-05 15:04:07 +01:00