Add OpenUSD module

[mgriley]

This adds an OpenUSD module, starting at version 25.11. It provides a target @openusd//:openusd to link OpenUSD as a C++ static library and a target @openusd//:plugin_files for specifying the default plugin files as a data dependency.

@bazel-io skip_check unstable_url

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (openusd) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

[gemini-code-assist]

Code Review

This pull request adds a new Bazel module for OpenUSD version 25.11. The module is well-structured, providing a monolithic static library and a test to verify the build, which aligns with the BCR guidelines.

My review has identified a few high-severity issues that should be addressed:

• There is a redundant MODULE.bazel file in the overlay directory which should be removed.
• The BUILD file in the overlay hardcodes build parallelism, which should be left for Bazel to manage.
• The new README.md contains user-specific paths in example commands, which should be replaced with placeholders.
• Additionally, the README.md file should be placed within the version-specific directory (25.11/) as suggested by the BCR style guide for better version-specific documentation.

Once these points are addressed, this will be a great addition to the BCR.

[gemini-code-assist]

Similar to the -j16 build argument, hardcoding CMAKE_BUILD_PARALLEL_LEVEL is not recommended. This overrides Bazel's job management. Please remove this environment variable to allow Bazel to control build parallelism.

[mgriley]

I don't think bazel cmake() rule with set this properly unless we specify it.

[fmeum]

The comment is somewhat accurate: Bazel doesn't know that this will use 16 jobs, so it will likely run too many actions concurrently, which could slow down the overall progress or consume too much memory.

[fmeum]

The comment is somewhat accurate: Bazel doesn't know that this will use 16 jobs, so it will likely run too many actions concurrently, which could slow down the overall progress or consume too much memory.

[mgriley]

@fmeum , is the best practice to remove both the -j<threads> and CMAKE_BUILD_PARALLEL_LEVEL here?

[mgriley]

I changed this to use CMAKE_BUILD_PARRALEL_LEVEL of 4 here, which seems like a reasonable compromise. Most of the other uses of the cmake() rule I've seen seem to do the same.

[mgriley]

@bazel-io skip_check unstable_url

[mgriley]

CC @dgoel - This is the PR to add OpenUSD to the bazel central registry.