Replies: 3 comments 1 reply
|
Hello! It's not possible to build those from source since they are not public, however, we will provide instructions on how to build MayaUSD using the devkit which contains the lib/include of these shared components. We've logged a ticket internally to keep track of that and get it done. Thanks! |
|
Hello @carpinc, We are also concerned about this. We build MayaUSD from source to apply local changes, but also to build against a custom OpenUSD version. Will this still be possible while keeping access to these shared components? Thanks, |
|
Sure @seando-adsk, We are building MayaUSD for Maya 2026, currently against USD v25.11. It’s important for us to keep some control over the USD version independently from the Maya version. During a long-running project, upgrading to a new major Maya version is usually not something we can do, but we still want to stay aligned with the USD version used by other parts of our pipeline, such as our renderer, and be able to upgrade USD when needed. Of course, as long as the MayaUSD source code is compatible with the USD version we use. Thank you, |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
We are building the v0.36.0 Plugin for 2027 on Linux from source but get a few messages about missing packages
comparing to the latest RPM, the libs and headers are being distributed there.
Would be possible to build these from source too ?
thanks!
All reactions