# Dependency Management for Libraries

**URL:** <https://discourse.processing.org/t/dependency-management-for-libraries/18940>\
**Category:** Development\
**Created:** [March 23, 2020, 4:31pm UTC](https://discourse.processing.org/t/dependency-management-for-libraries/18940 "2020-03-23T16:31:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jeremydouglass](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/jeremydouglass/32/20_2.png) [@jeremydouglass](https://discourse.processing.org/u/jeremydouglass)\
**Post date:** [June 25, 2020, 6:41pm UTC](https://discourse.processing.org/t/dependency-management-for-libraries/18940/3 "2020-06-25T18:41:04Z")

</div>

A recent related discussion regarding similar issues with Box2D rather than OpenCV:

> [@What's the best way to handle multiple libraries using the same imports](https://discourse.processing.org/t/whats-the-best-way-to-handle-multiple-libraries-using-the-same-imports/20577/2):
>
> I believe that this is here: cross-linking: The issue is not just that they are using the same underlying library – it is also that they might be using different versions of that library. Previous discussions: [https://forum.processing.org/two/discussion/577/boxwrap2d-vs-pbox2d](https://forum.processing.org/two/discussion/577/boxwrap2d-vs-pbox2d)[https://forum.processing.org/two/discussion/1040/how-to-deploy-library-that-requires-processing-s-serial-class](https://forum.processing.org/two/discussion/1040/how-to-deploy-library-that-requires-processing-s-serial-class) One approach would be to create a fork of any or all of them, Box2DThin, FisicaThin, LiquidFunThin t…

---

_[View the full topic](https://discourse.processing.org/t/dependency-management-for-libraries/18940)._