e5d1511d5b
It makes sense to allow platform definitions to opt out of having libc at all. One use case would be targetting some obscure new Linux target that doesn't have a libc implementation yet, and another is UEFI, which is basically libc-less Windows. Not having libc is not commonly specified in (GNU) triples (even Linux's build system will just target either -gnu or -musl depending on the platform), so instead, we use a separate attribute for it. |
||
|---|---|---|
| .. | ||
| architectures.nix | ||
| default.nix | ||
| doubles.nix | ||
| examples.nix | ||
| flake-systems.nix | ||
| inspect.nix | ||
| parse.nix | ||
| platforms.nix | ||