Implement workflow for a BIG-controlled cmake branch that is merged into Pixar's dev branch

[pmolodo]

Description

Pixar has already indicated they're willing to do this - this is just and issue for tracking the work to make sure this happens.

Champion

• Paul Molodowitch (pmolodowitch@nvidia.com) - @elrond79

Implementation Leads

• Paul Molodowitch (pmolodowitch@nvidia.com) - @elrond79

[pmolodo]

As a preview, I've made a branch on my personal repo that merges the 4 cmake PRs we've made thus far:

https://github.com/pmolodo/OpenUSD/commits/AOUSD-BuildIG-CMake-Draft/

[pmolodo]

Asked this of Sunya/Jess/Shabaz on 2027-04-01:

Some questions:

• Where exactly will the branch live?
  • ie, will it be a branch on an AOUSD-controlled repo, that Pixar will then periodically merge from?
  • Or a branch on the Pixar repo, that we will be given push access to?
• When exactly in the release cycle do we imagine the cmake merge would happen? During the alpha period? Some fixed amount of time pre-alpha? (Say, 1 week before alpha?)
• What release would we target as the first time we employ this workflow?

[pmolodo]

Working on setting up a meeting with Pixar to hash out some details

[pmolodo]

TAC is behind this, and Pixar has given their approval in concept. However, we need to meet with them to discuss concrete implementation details - Jessica Wang, who usually handles scheduling, has been out the past 2 weeks, however.