08:37 <arianvp> andi-: I think that would also mean instead of relying on the auto-detect behaviour; also enable and disable the dependency flags automatically?

08:37 <arianvp> e.g. we can set -Dopenssl=false if we're not using openssl

08:49 <andi-> arianvp: that is something we could do. I wouldn't do it in the first iteration.

08:49 <andi-> Small incremental changes.

08:50 <arianvp> sound good

09:03 <arianvp> , withEfi ? stdenv.hostPlatform.isEfi

09:03 <{^_^}> Invalid command syntax

09:03 <arianvp> shouldn't this be targetPlatform

09:04 <arianvp> I always confuse these cross-compilation target names

09:27 <andi-> > The "host platform" is the platform on which a package will be run. This is the simplest platform to understand, but also the one with the worst name.

09:27 <{^_^}> error: syntax error, unexpected ',', expecting ')', at (string):494:112

09:27 <andi-> ,hostPlatform

09:27 <andi-> ,hostPlatform = The "host platform" is the platform on which a package will be run. This is the simplest platform to understand, but also the one with the worst name. (https://nixos.org/manual/nixpkgs/stable/#chap-cross)

09:27 <{^_^}> hostplatform defined

09:28 <andi-> ,buildPlatform = The "build platform" is the platform on which a package is built. Once someone has a built package, or pre-built binary package, the build platform should not matter and can be ignored. (https://nixos.org/manual/nixpkgs/stable/#chap-cross)

09:28 <{^_^}> buildplatform defined

09:45 <qyliss> arianvp: targetPlatform is only for if you're building a compiler or similar

09:45 <qyliss> it's for, like, "what arcitecture will this gcc build executables for"

09:46 <qyliss> i.e. you could build a gcc on x86_64 (buildPlatform), that runs on aarch64 (hostPlatform), and produces riscv executables (targetPlatform)