I have a shell that comes from this use of Naersk. When I open a shell, it pre-builds all my dependencies. The naersk docs show just throwing rustc and cargo into a mkShell but that isn't sufficient for the case I show below. Is there a way to ask naersk to stop prebuilding and just use buildPackage for my shell?

naersk-lib.buildPackage {
          src = ./.;

          nativeBuildInputs = with pkgs; [
            clang
            cpiotools.defaultPackage.${system}
            grub2_efi
            jq
            nix
            pkgsStatic.pkg-config
            pkgsStatic.stdenv.cc
            qemu
            rustfmt
            which
            vim # xxd
          ];
          buildInputs = with pkgs; [ pkgsStatic.zstd cryptsetupStatic rustPlatform.bindgenHook ];

          OVMF_PATH = pkgs.OVMF.fd;

          # Configures the target which will be built.
          # ref: https://doc.rust-lang.org/cargo/reference/config.html#buildtarget
          CARGO_BUILD_TARGET = "x86_64-unknown-linux-musl";

          # Enables static compilation.
          #
          # If the resulting executable is still considered dynamically
          # linked by ldd but doesn't have anything actually linked to it,
          # don't worry. It's still statically linked. It just has static
          # position independent execution enabled.
          # ref: https://github.com/rust-lang/rust/issues/79624#issuecomment-737415388
          CARGO_BUILD_RUSTFLAGS = "-C target-feature=+crt-static";

          # Configures the linker which will be used. cc.targetPrefix is
          # sometimes different than the targets used by rust. i.e.: the
          # mingw-w64 linker is "x86_64-w64-mingw32-gcc" whereas the rust
          # target is "x86_64-pc-windows-gnu".
          #
          # This is only necessary if rustc doesn't already know the correct linker to use.
          #
          # ref: https://doc.rust-lang.org/cargo/reference/config.html#targettriplelinker
          CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_LINKER = with pkgs.pkgsStatic.stdenv;
            "${cc}/bin/${cc.targetPrefix}gcc";
          # link against libc.a
          CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_RUSTFLAGS = "-lc";

          doCheck = true;
        };

In reply to @grahamc:nixos.org

I have a shell that comes from this use of Naersk. When I open a shell, it pre-builds all my dependencies. The naersk docs show just throwing rustc and cargo into a mkShell but that isn't sufficient for the case I show below. Is there a way to ask naersk to stop prebuilding and just use buildPackage for my shell?

naersk-lib.buildPackage {
          src = ./.;

          nativeBuildInputs = with pkgs; [
            clang
            cpiotools.defaultPackage.${system}
            grub2_efi
            jq
            nix
            pkgsStatic.pkg-config
            pkgsStatic.stdenv.cc
            qemu
            rustfmt
            which
            vim # xxd
          ];
          buildInputs = with pkgs; [ pkgsStatic.zstd cryptsetupStatic rustPlatform.bindgenHook ];

          OVMF_PATH = pkgs.OVMF.fd;

          # Configures the target which will be built.
          # ref: https://doc.rust-lang.org/cargo/reference/config.html#buildtarget
          CARGO_BUILD_TARGET = "x86_64-unknown-linux-musl";

          # Enables static compilation.
          #
          # If the resulting executable is still considered dynamically
          # linked by ldd but doesn't have anything actually linked to it,
          # don't worry. It's still statically linked. It just has static
          # position independent execution enabled.
          # ref: https://github.com/rust-lang/rust/issues/79624#issuecomment-737415388
          CARGO_BUILD_RUSTFLAGS = "-C target-feature=+crt-static";

          # Configures the linker which will be used. cc.targetPrefix is
          # sometimes different than the targets used by rust. i.e.: the
          # mingw-w64 linker is "x86_64-w64-mingw32-gcc" whereas the rust
          # target is "x86_64-pc-windows-gnu".
          #
          # This is only necessary if rustc doesn't already know the correct linker to use.
          #
          # ref: https://doc.rust-lang.org/cargo/reference/config.html#targettriplelinker
          CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_LINKER = with pkgs.pkgsStatic.stdenv;
            "${cc}/bin/${cc.targetPrefix}gcc";
          # link against libc.a
          CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_RUSTFLAGS = "-lc";

          doCheck = true;
        };

In reply to @dpc:matrix.org
Where's the problem?

In reply to@tengkuizdihar:matrix.org
my problem is about how to do it at all. I've followed non-nixos way to do it to no avail.

in what way is it not working? what have you done so far? Does it show up? is the extension installed in vscode already? is the extension erroring?

In reply to @qyliss:fairydust.space
hey, it's been a while since I needed a beta/nightly Rust compiler. Is oxalica's Rust overlay still the thing to use?