• TheTrueLinuxDev@beehaw.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    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.devOP
      link
      fedilink
      English
      arrow-up
      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.org
        link
        fedilink
        English
        arrow-up
        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.is
      link
      fedilink
      English
      arrow-up
      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 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 = [ ];
      }
      
      • TheTrueLinuxDev@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Neither actually, I think the issues I encounter happened before the llvm/clang packages get renamed to llvmPackages_16.* and one of the approach I did was adding the nix-shell initialization into .bashrc at the time to workaround my ignorance of NixOS.

        There weren’t a lot of documentation to address my troubles with NixOS at the time, so yesterday evening, I reinstalled NixOS on a VM and started on reading up documentation to re-learn NixOS and trying to get it working. It still confusing however, but I’m taking my time to learn NixOS with a honest try.