In reply to @linus:schreibt.jetzt
Izdihar: ah, I think you also need gsettings-desktop-schemas in buildInputs

Hello! I think I have a basic question. First time trying to package a Rust project

        alexandria = naersk'.buildPackage {
          src = builtins.fetchGit {
            url = ssh://git@github.com/.../...;
            ref = "HEAD";
            rev = "asdas";
          };
          patches = [
            ./001-remove-buildinfo.patch
          ];
          gitAllRefs = true;
        };

The build fails applying the patch with:

can't find file to patch at input line 14                                                                                       
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

I looked at the derivation logs via nix logs and I checked the source archive directory but the files in there looks totally different compared with the one I have as part of the repository. Not sure why and as consequence the patch fails because it can't find all the files it should have

Hello! I think I have a basic question. First time trying to package a Rust project

        rust-test = naersk'.buildPackage {
          src = builtins.fetchGit {
            url = ssh://git@github.com/.../...;
            ref = "HEAD";
            rev = "asdas";
          };
          patches = [
            ./001-remove-buildinfo.patch
          ];
          gitAllRefs = true;
        };

The build fails applying the patch with:

can't find file to patch at input line 14                                                                                       
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

I looked at the derivation logs via nix logs and I checked the source archive directory but the files in there looks totally different compared with the one I have as part of the repository. Not sure why and as consequence the patch fails because it can't find all the files it should have

In reply to @tengkuizdihar:matrix.org
It's working now! No more errors! The worst part about it is that I need to probably wait for the next version of the package to get some of the fixes that's included in my patch... https://github.com/NixOS/nixpkgs/issues/189571#issuecomment-1253102758 Linux Hackerman

In reply to @dpc:matrix.org
But I can't figure out what exactly am I supposed to set to get something to run? I just need to chmod +x some files that were copied into the derivation.

Anyone know of a cross-compilation example that targets musl and uses rust-overlay?

I can't for the life of me figure this out. I've spent the past couple of hours trying to search and read up on it, but I feel like there's some crucial tidbits of ignorance that keep me in the dark.
All the rust docs refer to leveraging rustup, which AFAIU is kinda antheisis to the premise of Nix.

I'm finding the learning curve a bit too steep for me =/

I've attempted:

• rust-toolchain.toml; ```toml
  [toolchain]
  targets = ["x86_64-unknown-linux-musl", "x86_64-unknown-linux-gnu"]

  `flake.nix`: ```nix
    overlays = [
      (import rust-overlay)
      (self: super: {
        rustToolchain =
          let
            rust = super.rust-bin;
          in
          if builtins.pathExists ./rust-toolchain.toml then
            rust.fromRustupToolchainFile ./rust-toolchain.toml
          else if builtins.pathExists ./rust-toolchain then
            rust.fromRustupToolchainFile ./rust-toolchain
          else
            rust.stable.latest.default;
      })
    ]
  

  And finally; cargo build --target 'x86_64-unknown-linux-musl'

Anyone know of a cross-compilation example that targets musl and uses rust-overlay?

I can't for the life of me figure this out. I've spent the past couple of hours trying to search and read up on it, but I feel like there's some crucial tidbits of ignorance that keep me in the dark.
All the rust docs refer to leveraging rustup, which AFAIU is kinda antheisis to the premise of Nix.

I'm finding the learning curve a bit too steep for me =/

I've attempted:

• rust-toolchain.toml;

  [toolchain]
  targets = ["x86\_64-unknown-linux-musl", "x86\_64-unknown-linux-gnu"]
  
  

  flake.nix:

    overlays = [
      (import rust-overlay)
      (self: super: {
        rustToolchain =
          let
            rust = super.rust-bin;
          in
          if builtins.pathExists ./rust-toolchain.toml then
            rust.fromRustupToolchainFile ./rust-toolchain.toml
          else if builtins.pathExists ./rust-toolchain then
            rust.fromRustupToolchainFile ./rust-toolchain
          else
            rust.stable.latest.default;
      })
    ]
  

  And finally; cargo build --target 'x86_64-unknown-linux-musl'

As mentioned in the https://matrix.to/#/#nix:nixos.org channel, the end result I'm looking for is a reduction of my docker image;

# flake.nix
      # The rust binary
      cargo-details = (pkgs.lib.importTOML ./Cargo.toml);
      binary-name = cargo-details.package.name;
      binary-version = cargo-details.package.version;
      cargo-package = pkgs.rustPlatform.buildRustPackage {
        pname = binary-name;
        version = binary-version;

        src = self;
        cargoLock.lockFile = ./Cargo.lock;

        nativeBuildInputs = rust-tools;
        buildInputs = rust-tools;
      };

      # Docker image
      # TODO: Reduce container size (cargo release -> ~5MB vs docker image -> ~35MB)
      # Seems like glibc is at fault? Statically compile? Musl?
      #  -> $ tree -L 3 unpacked_dockerimage/layer/
      #  unpacked_dockerimage/layer/
      #  └── nix
      #      └── store
      #          ├── 39pvnhy2l6zlqrgh6vv861v8lj6wnz0r-assign-item-to-project-field-0.1.0
      #          ├── 6f66prpgx1qx4n6k450sxs3d157ia1ps-glibc-2.35-163
      #          ├── g7lwga9p547cqyi9ym35bk78m1r12rky-libunistring-1.0
      #          └── jna5qh81395w6xsalnl532pm9qvvvpjy-libidn2-2.3.2
      #
      #  6 directories, 0 files
      #  -> $ sudo du -hs unpacked_dockerimage/layer/nix/store/* | sort -h
      #  308K    unpacked_dockerimage/layer/nix/store/jna5qh81395w6xsalnl532pm9qvvvpjy-libidn2-2.3.2
      #  1,6M    unpacked_dockerimage/layer/nix/store/39pvnhy2l6zlqrgh6vv861v8lj6wnz0r-assign-item-to-project-field-0.1.0
      #  1,8M    unpacked_dockerimage/layer/nix/store/g7lwga9p547cqyi9ym35bk78m1r12rky-libunistring-1.0
      #  31M     unpacked_dockerimage/layer/nix/store/6f66prpgx1qx4n6k450sxs3d157ia1ps-glibc-2.35-163
      #
      docker-image = pkgs.dockerTools.buildImage {
        name = binary-name;
        tag = "v${binary-version}";
        config = {
          Cmd = ["${cargo-package}/bin/${binary-name}"];
        };
      }

Anyone know of a cross-compilation example that targets musl and uses rust-overlay?

I can't for the life of me figure this out. I've spent the past couple of hours trying to search and read up on it, but I feel like there's some crucial tidbits of ignorance that keep me in the dark.
All the rust docs refer to leveraging rustup, which AFAIU is kinda antheisis to the premise of Nix.

I'm finding the learning curve a bit too steep for me =/

I've attempted:

• rust-toolchain.toml;

[toolchain]
targets = ["x86\_64-unknown-linux-musl", "x86\_64-unknown-linux-gnu"]

flake.nix:

  overlays = [
    (import rust-overlay)
    (self: super: {
      rustToolchain =
        let
          rust = super.rust-bin;
        in
        if builtins.pathExists ./rust-toolchain.toml then
          rust.fromRustupToolchainFile ./rust-toolchain.toml
        else if builtins.pathExists ./rust-toolchain then
          rust.fromRustupToolchainFile ./rust-toolchain
        else
          rust.stable.latest.default;
    })
  ]

And finally; cargo build --target 'x86_64-unknown-linux-musl'

Anyone know of a cross-compilation example that targets musl and uses rust-overlay?

I can't for the life of me figure this out. I've spent the past couple of hours trying to search and read up on it, but I feel like there's some crucial tidbits of ignorance that keep me in the dark.
All the rust docs refer to leveraging rustup, which AFAIU is kinda antheisis to the premise of Nix.

I'm finding the learning curve a bit too steep for me =/

I've attempted:

• rust-toolchain.toml;

[toolchain]
targets = ["x86\_64-unknown-linux-musl", "x86\_64-unknown-linux-gnu"]

flake.nix:

  overlays = [
    (import rust-overlay)
    (self: super: {
      rustToolchain =
        let
          rust = super.rust-bin;
        in
        if builtins.pathExists ./rust-toolchain.toml then
          rust.fromRustupToolchainFile ./rust-toolchain.toml
        else if builtins.pathExists ./rust-toolchain then
          rust.fromRustupToolchainFile ./rust-toolchain
        else
          rust.stable.latest.default;
    })
  ]

And finally; cargo build --target 'x86_64-unknown-linux-musl'

Anyone know of a cross-compilation example that targets musl and uses rust-overlay?

I can't for the life of me figure this out. I've spent the past couple of hours trying to search and read up on it, but I feel like there's some crucial tidbits of ignorance that keep me in the dark.
All the rust docs refer to leveraging rustup, which AFAIU is kinda antheisis to the premise of Nix.

I'm finding the learning curve a bit too steep for me =/

I've attempted:
rust-toolchain.toml;

[toolchain]
targets = ["x86\_64-unknown-linux-musl", "x86\_64-unknown-linux-gnu"]

flake.nix:

  overlays = [
    (import rust-overlay)
    (self: super: {
      rustToolchain =
        let
          rust = super.rust-bin;
        in
        if builtins.pathExists ./rust-toolchain.toml then
          rust.fromRustupToolchainFile ./rust-toolchain.toml
        else if builtins.pathExists ./rust-toolchain then
          rust.fromRustupToolchainFile ./rust-toolchain
        else
          rust.stable.latest.default;
    })
  ]

And finally; cargo build --target 'x86_64-unknown-linux-musl'

Zhaofeng Li: AFAICT this does not use rust-overlay?

I am for sure not able to parse your flake.nix. I looked into crane - and after reading what its README says, I can't tell how you add musl as a cross-compilation target?