Help. I'm trying to port my fenix toolschain setup to crane and:

      fenix-pkgs = fenix.packages.${system};
      fenix-channel = fenix-pkgs.stable;

      craneLib = (crane.mkLib pkgs).overrideScope' (final: prev: {
        # inherit (fenix-channel) cargo rustc;
      });

I can't uncomment that line because it breaks everything. AFAICT, that's what I was more or less doing in naersk

Hmm...

Found something that works.

      fenix-pkgs = fenix.packages.${system};
      fenix-channel = (fenix-pkgs.stable);

      craneLib = (crane.mkLib pkgs).overrideScope' (final: prev: {
        cargo = fenix-channel.cargo;
        rustc = fenix-channel.rustc;
      });

Is this the right way then?

In reply to @js:ukvly.org

or for me on nixos 21.11:

error: /nix/store/qjgj2642srlbr59wwdihnn66sw97ming-glibc-2.33-123/lib/libpthread.so.0: undefined symbol: __libc_siglongjmp, version GLIBC_PRIVATE
   --> /home/julian/.cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro-error-1.0.4/src/lib.rs:284:9
    |
284 | pub use proc_macro_error_attr::proc_macro_error;
    |         ^^^^^^^^^^^^^^^^^^^^^

In reply to @dpc:matrix.org
I am hitting this problem all the time myself. The reason is that normal cargo/rustup are impure. The only reliable solution I've found is to use nix flakes + lorri for everything on NixOs.

Does anyone have examples how to deal with a build.rs script like this?:
https://github.com/raduzaharia-medium/gtk-rss-reader-resource/blob/main/build.rs

fn main() {
    compile_resources(
        "content",
        "content/app.gresource.xml",
        "gtk-rss-reader.gresource",
    );
}

In reply to @dpc:matrix.org
In a nixifified project using flakes, do you check-in the .envrc file into git, or is every contributor expected to create it if they use something like lorri?

In reply to @a-kenji:matrix.org
I usually am just adding use_flake, but other people might want a different .envrc.

In reply to @vika:fireburn.ru
Why wouldn't you use a Nix-based environment if you have nix installed? I made my .envrc a no-op on systems that don't have nix in PATH, but for people who have it, they gonna get the same environment I use everywhere (if they choose to allow the .envrc to run)

In reply to @a-kenji:matrix.org
Some people don't have flakes enabled, some might use a different invocation - with lorri / sorri / have their own nix-shell caching. This probably won't happen to many people, but every now and then I think about how this can be made a little bit more universal.

In reply to @vika:fireburn.ru
One could build detection for common workflows like lorri/sorri too. Having flakes disabled is also a valid concern, but once again, this could be potentially detected and handled