nixos module

[Mic92]

No description provided.

[VanCoding]

@Mic92 whoa, that was quick!

I came up with the following today:

# nix-ld.nix
{config, lib, pkgs, ...}:{
  programs.nix-ld.enable = true;
  environment.variables = {
      NIX_LD_LIBRARY_PATH = lib.makeLibraryPath (config.systemd.packages ++ config.environment.systemPackages);
      NIX_LD = "${pkgs.glibc}/lib/ld-linux-x86-64.so.2";
  };
}

I don't know excatly how the module system works, but my assumption was that for systemd.packages and environment.systemPackages to contain all configured packages, it would have to run at the very last, even after the main configuration.nix file. So in the system configuration flake, I'd import the above module after configuration.nix file like so:

{
  description = "My NixOS configuration";
  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
  };
  outputs = {self,nixpkgs, }:{
    nixosConfigurations.my-machine = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [
         ./configuration.nix
         ./nix-ld.nix
      ];
      specialArgs = { inherit nixpkgs; };
    };
  };
}

But I couldn't login to gnome after this 😓 and I discarded it. But it'd still be cool, if nix-ld would somehow detect all the libraries that are installed on the system anyway and make them available. Having a list of "common" libs is probably the better idea, but it also means that there will be stuff installed that's probably not needed.

[Mic92]

I think I would probably in the beginning just leave it to the user what libraries to install since everyone needs something else. Discovering all libraries sounds tricky - it would likely cause conflicts and its unclear which library should be preferred in this case.

[Quoteme]

In line 8 you added a closing brace which never got opened, it seems