# represent Mac Catalyst as aarch64-maccatalyst-none rather than aarch64-ios-macabi · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/9ab7eec23e6aa1fc8d5659566e426816ba573537)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 9ab7eec23e6aa1fc8d5659566e426816ba573537

Requested commit: 9ab7eec23e6aa1fc8d5659566e426816ba573537

Commit: 9ab7eec23e6aa1fc8d5659566e426816ba573537

Tree: b6b7bbdbccd75ced24eeb677959d41be06b311ff

Author: Alex Rønne Petersen

Committer: Alex Rønne Petersen

## Message

```
represent Mac Catalyst as aarch64-maccatalyst-none rather than aarch64-ios-macabi

Apple's own headers and tbd files prefer to think of Mac Catalyst as a distinct
OS target. Earlier, when DriverKit support was added to LLVM, it was represented
a distinct OS. So why Apple decided to only represent Mac Catalyst as an ABI in
the target triple is beyond me. But this isn't the first time they've ignored
established target triple norms (see: armv7k and aarch64_32) and it probably
won't be the last.

While doing this, I also audited all Darwin OS prongs throughout the codebase
and made sure they cover all the tags.

```

## Parents

- [2e6f7d36b9292b2a88a28c3caab767cd9401175d](https://git.cafe/gitcafe/zig/commit/2e6f7d36b9292b2a88a28c3caab767cd9401175d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/9ab7eec23e6aa1fc8d5659566e426816ba573537?format=markdown)