| 27 Jun 2025 |
 Tristan Ross | In reply to @emilazy:matrix.org
I'm not aware of any current work on that front (for C-family languages I'm not sure it's a good idea to split up, though stdenvNoCC by default would obviously be great but is a hugely breaking change for external users) We've already got split GCC on the way and so far, it's doing good. | 21:35:20 |
| Tristan Ross | I was thinking of having derivations which mirror the toolchain attributes | 21:35:46 |
| Tristan Ross | So cc is your C/C++ compiler while cxxlib would be your C++ std implementation. | 21:36:19 |
| Tristan Ross | Ik it's something I've talked to Jon about | 21:37:22 |
| Tristan Ross | And it's in the stdenv & CC improvements plan | 21:37:39 |
| 28 Jun 2025 |
 Randy Eckenrode | I’ve been wondering if we should generate a sysroot when setting up the stdenv and point the compiler to that. It would simplify the Darwin SDK and let me drop some workarounds in the Swift compiler. | 00:30:39 |
| Randy Eckenrode | I would also like to see the stdenv not assume a C compiler and require it (and autotools/make support) to be added just like for every other language and build system. | 00:33:07 |
| Tristan Ross | Yeah, it'll be great to disconnect stdenv and cc | 00:33:53 |
