SUPPORT FOR MACOS x86_64 (Intel Chip) for kit-app-template repo

Omniverse Core Platform Kit App Template / SDK
,
1

Is there any planned support for Intel chip Mac os laptops for Kit-app-template repo.

I run codex on vscode to try and fix the issue and this is what it spat back at me:

Title: Intel macOS bootstrap/build is broken in kit-app-template (7zz arch mismatch, missing kit-kernel package for macos-x86_64)

Body:

## Summary

On an Intel Mac (`macos-x86_64`), `kit-app-template` does not currently bootstrap/build successfully.

I hit two distinct issues:

1. `./repo.sh template new` initially fails because Packman invokes an ARM-only `7zz` binary on Intel macOS.
2. After working around that, `./repo.sh build` fails because it tries to fetch a Kit package that does not appear to exist on the configured remotes:
   `kit-kernel@110.0.0+feature.macos-x86_64.release`

This makes the template unusable on Intel macOS in its current state.

## Environment

- Repo: `NVIDIA-Omniverse/kit-app-template`
- Host OS: macOS
- Host arch: `x86_64`
- Date observed: April 1, 2026

## Reproduction

### 1. Bootstrap/template creation

```bash
./repo.sh template new

Initial failure:

OSError: [Errno 86] Bad CPU type in executable: '/Users/.../packman-cache/chk/7zz/25.01/mac-arm/64/7zz'

The failing path is explicitly:

.../packman-cache/chk/7zz/25.01/mac-arm/64/7zz

On this machine:

uname -m
# x86_64

2. Build

After working around the above locally, I ran:

./repo.sh build

and got:

BuildError: An error occured while pulling packman dependencies for
`.../tools/deps/kit-sdk.packman.xml`:
Package not found on specified remote servers!
(name: kit-kernel, version: 110.0.0+feature.macos-x86_64.release)

Additional findings

A. packman-common 7.34 appears to hardcode macOS 7zz to mac-arm

The cached archive7z.py selected mac-arm for Darwin, which is wrong on Intel macOS.

Observed behavior:

  • host is x86_64
  • Packman chooses .../chk/7zz/25.01/mac-arm/64/7zz
  • execution fails with Bad CPU type in executable

This looks like a platform-selection bug in Packman / packman-common.

B. repo_build / token handling around platform_target_abi on macOS is inconsistent

During investigation, platform_target_abi was being removed for macos-x86_64, while tools/deps/kit-sdk.packman.xml expects it in:

<package name="kit-kernel" version="110.0.0+feature.${platform_target_abi}.${config}"/>

Even after fixing that locally so platform_target_abi resolves to macos-x86_64, the next failure is still that the remote package does not exist.

So there may be two upstream questions:

  • should platform_target_abi resolve to platform_target on macOS?
  • is macos-x86_64 intentionally unsupported for Kit 110, or is the package naming/publication wrong?

Expected behavior

One of the following should be true:

  • Intel macOS is supported:
    • Packman should select a compatible macOS 7zz
    • repo.sh build should resolve a valid published kit-kernel package for macos-x86_64

or

  • Intel macOS is not supported:
    • the repo should fail early with a clear, explicit unsupported-platform message instead of failing deep in Packman/package resolution

Actual behavior

The repo fails in a way that looks broken rather than intentionally unsupported:

  • wrong 7zz architecture chosen on bootstrap
  • missing Kit package requested during build

Request

Could you confirm whether macos-x86_64 is meant to be supported for this template and Kit version?

If yes, this likely needs:

  • a Packman/packman-common fix for Darwin 7zz selection on Intel macOS
  • a fix to Kit package naming/publication or dependency resolution for kit-kernel@110.0.0+feature.macos-x86_64.release

If no, it would help to document that clearly and add an early guard in the template/build flow.


If you want, I can also turn this into a shorter, more maintainers-friendly version.
2

Omniverse does not run natively on Intel‑chip macOS laptops and is officially supported only on Windows and Linux systems with an NVIDIA RTX GPU. forums.developer.nvidia

Current support status

  • NVIDIA staff state that Omniverse “can never run directly on the Mac OS platform” because it depends on RTX ray‑tracing hardware, and Macs do not support NVIDIA RTX GPUs or drivers. forums.developer.nvidia
  • This applies to both Intel and Apple‑silicon Macs: there is no supported Omniverse desktop build for macOS, and you cannot work around it with Boot Camp or similar because the hardware GPU requirement is still not met. reddit

What is possible with a Mac

  • Use a remote Windows or Linux workstation or cloud VM with an RTX GPU to run Omniverse, and connect from your Mac via:
    • Omniverse’s web or streaming clients (e.g., Spatial Streaming / browser clients). docs.omniverse.nvidia
    • Standard remote‑desktop tools while Omniverse runs on the RTX machine.
  • You can also develop client‑side or web tooling on macOS that talks to Omniverse services running remotely, but the full RTX Omniverse apps do not execute locally on the Mac. docs.omniverse.nvidia
3

ok, this is sad to know. Thank you for this information.

4

Well it is easily solved, by just getting a PC or by renting a PC, through a cloud provider. We have NVIDIA Brev which runs on PC Linux and it works great.