Dependencies
If software has dependencies, it means it depends on other software.
Often there’s a distribution system to install these dependencies. e.g. pip
There’s a link from the software to it’s dependencies.
often a dependency has
- A checksum
- A location
- A name
- A version
https://matklad.github.io/2024/12/30/what-is-dependency.html?utm_source=tldrnewsletter
Backlinks¶
- Maya plugin
- There is no native support for dependencies on:
- versioning
- Handling multiple versions of something,
- Unreal python plugin template
- the included Unreal dependencies installer auto installs dependencies on Unreal startup from
requirements.txt
- the included Unreal dependencies installer auto installs dependencies on Unreal startup from
- plugget - create a self-installing plugin
- replaced plugget vendor with Unreal dependencies installer, which uses py-pip, a simpler solution for Unreal. Less good for plugget.
But plugget has more dependencies, and the extra 3 Mb vendor size seems too bloated.
- replaced plugget vendor with Unreal dependencies installer, which uses py-pip, a simpler solution for Unreal. Less good for plugget.
- vendoring
- Vendoring means copying the source code of another project into your project
- Maya plugin manager
- plugin dependencies
- Unreal dependencies installer
- Auto install Python module dependencies in Unreal, using py-pip.
- expose a python tool in plugget without wrapping it
- Currently, I always wrap a tool in a wrapper plugin, publishing it in its own GitHub repo.
- ensure fbx plugin is loaded in Maya
- dependencies between 2 Maya plugins