# The 'default' package is the package injected into our package set

          # But the package set also has a pkgsCross set, and we can select our package from one of its contents
          packages.cross-riscv64 = pkgs.pkgsCross.riscv64.wttr-delft;

, Packaging in this way and making use of the sandboxed Nix build process can hepl find missing dependencies etc.

, Packaging in this way and making use of the sandboxed Nix build process
, can help find dependencies that were not correctly declared etc.

, The previous build was for x86_64-linux by default because that is our current system:
x "${file_cmd}" ./result/bin/wttr-delft

, We can very easily set up cross-compilation.

h We can very easily set up cross-compilation.

, If we take a look at what the flake provides:

, Now we can call a different output:
x nix build "${dir}#cross-riscv64"
, And this is indeed a RISC-V binary:
x "${file_cmd}" ./result/bin/wttr-delft
h Emulation
, If we take a look at what the flake provides we see multiple architectures as well:

h The previous build was for x86_64-linux by default because that is our current system:
x "${file_cmd}" ./result/bin/wttr-delft

n This will not work if the emulation is not available:
, But, if you use NixOS it\'s also very simple to set up binfmt to emulate e.g. aarch64-linux!

h But we can easily build for aarch64-linux \(e.g. for Raspberry Pi\):

n If you use NixOS it\'s also very simple to set up binfmt to still be able to run the binary!