# How to build usd to allow for static linking

**URL:** <https://forum.aousd.org/t/how-to-build-usd-to-allow-for-static-linking/2094>\
**Category:** Build and Deployment\
**Created:** [December 19, 2024, 3:07pm UTC](https://forum.aousd.org/t/how-to-build-usd-to-allow-for-static-linking/2094 "2024-12-19T15:07:03Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dhruvgovil](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.aousd.org/dhruvgovil/32/3_2.png) [@dhruvgovil](https://forum.aousd.org/u/dhruvgovil)\
**Post date:** [December 26, 2024, 4:12pm UTC](https://forum.aousd.org/t/how-to-build-usd-to-allow-for-static-linking/2094/6 "2024-12-26T16:12:21Z")

</div>

You’ll need the plugin search to still look for the plugInfo.json to find what to register. See my PR above.

The JSON files still include various metadata about how each plugin is used, which is why they can’t simply be elided.

However I think it might be worth having a setup where static or monolithic builds pull the JSON data as internalized static data.

---

_[View the full topic](https://forum.aousd.org/t/how-to-build-usd-to-allow-for-static-linking/2094)._