Kit 108 doesn't compile after creating extension

Omniverse Core Platform
1

Hi

I am trying to create a extension c++ with python bindings. after app creation if I use ./repo.sh build it works properly, after that I create a pure c++ or c++ with python bindings ./repo.sh build stops working;

Callstack:
Creating ../../../_build/intermediate/linux-x86_64/my_company.my_cpp_extension.plugin/x86_64/release
Creating ../../../_build/linux-x86_64/release/exts/my_company.my_cpp_extension/bin
CppExtension.cpp
/bin/sh: 1: g++: not found
make[1]: *** [Makefile:163: ../../../_build/intermediate/linux-x86_64/my_company.my_cpp_extension.plugin/x86_64/release/CppExtension.o] Error 127
make: *** [Makefile:40: my_company.my_cpp_extension.plugin] Error 2
[09/23/25 13:12:30] ERROR error running: [‘make’, ‘–directory=/projects/ngcspacesim/renderer/_compiler/gmake2’, ‘–stop’, ‘config=release_x86_64’, ‘-j12’, ‘–output-sync’], code: 2, utils.py:360
message: “”
WARNING Retrieving repo_build version via VERSION file. version.py:312
ERROR BuildError exception stack trace dumped to logfile /projects/censoredname/renderer/_repo/repo.log. Stacks dumped to console via --verbose or --tracebacks. log.py:182
BuildError: BUILD FAILED for release

2

The issue in the build process for your Omniverse C++ extension (with or without Python bindings) is that the g++ compiler is not found during the build step. The call stack in your log shows:

text

/bin/sh: 1: g++: not found
make[1]: *** [Makefile:163: .../CppExtension.o] Error 127
make: *** [Makefile:40: my_company.my_cpp_extension.plugin] Error 2
...
BuildError: BUILD FAILED for release

This error occurs because the build system, when building C++ code, expects the g++ tool (the GNU C++ compiler) to be available in your system’s PATH. When it cannot find g++, the build will immediately stop with the reported error.

Why Does It Only Fail With C++ Extensions?

  • Pure Python parts of Omniverse extensions do not require a C++ compiler during build, so the absence of g++ goes unnoticed.
  • When you add any C++ code (including native or with Python bindings), the build system tries to call g++ to compile .cpp files, which fails if the compiler is missing.

How To Fix

  • Install g++:
    • On Ubuntu/Debian:
      sudo apt install g++
    • On CentOS/RHEL:
      sudo yum install gcc-c++
    • On Windows (with Cygwin/MinGW): Install the corresponding C++ compiler and make sure its directory is included in your system’s PATH.
  • After installing, verify with:
    g++ --version
    If this command returns a version number, it is correctly installed.

Common Follow-Up Steps

  • After installation, re-run ./repo.sh build.
  • Ensure your build environment (IDE, VS Code, terminal) is restarted or reloaded so the updated PATH is recognized.

Your issue is a standard missing-tool problem when moving to C++ or C++/Python hybrid Omniverse extensions.

3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.