Build folder structure of Autodesk fork of USD
- Dominant language
- C++
- Stars
- 620
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
It is mentioned that [Autodesk fork of USD](https://github.com/autodesk-forks/USD/tree/adsk/feature/hgiraytracing) is used.
- By running the steps in https://github.com/Autodesk/Aurora#quick-start
- The source of Autodesk fork of USD should be downloaded into AuroraExternals\src\USD-22.08-Aurora-v22.11
- The **build of Autodesk fork of USD is in AuroraExternals\build\USD-22.08-Aurora-v22.11**? This folder structure is quite **different (specifically, no plugin and lib folder) than the build folder of official USD** and does **not contain usdview.cmd**. **[deployHdAurora.py](https://github.com/Autodesk/Aurora/blob/main/Scripts/deployHdAurora.py) should target this folder**?
if deployHdAurora.py to an empty folder, there will be bin, lib, and plugin sub-folders, well, **AuroraExternals\Release contains these sub-folders**.
Contributor guide
Research direction
Run the steps in the Aurora Quick Start and inspect AuroraExternals/src/USD-22.08-Aurora-v22.11, AuroraExternals/build/USD-22.08-Aurora-v22.11, and AuroraExternals/Release. Then read Scripts/deployHdAurora.py and compare its target with the generated Autodesk USD layout; done means the script targets the correct folder and produces the expected bin, lib, and plugin structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100