In reply to @rosscomputerguy:matrix.org

There's a few things that I've been thinking of:

1. Docs wise, try and promote using packages.${system}.${name} over devShells due to runPhase and easy propagation of dependencies. inputsFrom is an option if a dev shell needs more stuff than just the package itself needs.
2. cpu attribute which tunes everything from FPU, CPU model, architecture, etc. Generic names could be supplied which sets all options. Support for different compilers would be better since it could have an attr set within each attribute that specifies what it should be for different compilers.
3. CC without wrappers, possibly a shell hook which extends CFLAGS or other things and adds the necessary flags we need.
4. stdenv without inheriting CC. Randy Eckenrode came up with this originally but I am thinking this might not be a bad idea. Tools like meson, cmake, etc could propagate cc which automatically should inject the hook.

In reply to @reckenrode:matrix.org
I’ve been advocating it, but I don’t think it was my idea. Maybe @emilazy:matrix.org?

In reply to @philiptaron:matrix.org
It's worth doing, even it it might mean moving away from the "stdenv" name.

In reply to @k900:0upti.me
Building arbitrary things for a UEFI target is generally not useful