• TheTrueLinuxDev@beehaw.orgEnglish
    2·
    1 year ago

    Don’t think so since the big part of what make arch appealing was the easier approach to programming on the platform. NixOS had some problems particularly the llvm and clang compilers that complained a lot about missing standard libraries and headers. Until that is addressed, it won’t be the new arch. I plan on trying it again on next weekend.

    • ericjmorey@programming.devOPEnglish
      2·
      1 year ago

      NixOS had some problems particularly the llvm and clang compilers that complained a lot about missing standard libraries and headers.

      I tried searching for LLVM related issues with NixOS, but came up empty. Could you help me find more info on this?

      • TheTrueLinuxDev@beehaw.orgEnglish
        1·
        1 year ago

        It was discussed on Matrix channel for NixOS a long while ago. I am re-attempting NixOS to see if they have addressed the QOL for Clang/LLVM development. That was some of the issues that come up when I was working with FFI LLVM-C with C# (it uses LLVM for accelerating LINQ operations.)

    • adisbladis@lemmy.blad.isEnglish
      1·
      1 year ago

      NixOS had some problems particularly the llvm and clang compilers that complained a lot about missing standard libraries and headers.

      I think it’s likely that you’re trying to just add clang/llvm toolchains to your development shell like this:

      pkgs.mkShell { packages = [
  llvmPackages_16.clang
]; };

      But you actually want something like:

      (mkShell.override { inherit (llvmPackages_16) stdenv; }) {
  packages = [ ];
}