I was used a modified Bullet with modified Panda3D for a long time. I needed to make a little changes for game networking to work.
Now I decided to split my modifications from Bullet and organize everything into separate packages.
The PIP with it’s EGG and WHL was not an option because it’s limited to Python packages and does not includes .H header files.
So I stick with the Miniconda Python, Conda manager and Anaconda Cloud.
I made a Conda package for a Bullet:
anaconda.org/kitsune.ONE/bullet (package)
launchpad.net/bullet-conda (recipe)
Then made a package with my little plugin for the Bullet:
anaconda.org/kitsune.one/bullet-kitsunetsuki (package)
launchpad.net/bullet-kitsunetsuki (recipe and code)
And made a package with a modified Panda3D:
anaconda.org/kitsune.one/panda3d-kitsunetsuki (package)
launchpad.net/panda3d-kitsunetsuki (recipe)
I had combined everything I need into my Conda environment: anaconda.org/kitsune.ONE/kitsunetsuki-dev
It’s so easy to use. With just one command I can install Panda3D with CMake and all packages that I need.
With the multiple Conda environments I was able to install multiple versions of Panda3D (with header files).
I also made a runtime package for my game for simplifying the deployment process:
anaconda.org/kitsune.ONE/kitsunetsuki-runtime (package)
launchpad.net/kitsunetsuki-runtime (recipe)
This is just a compact portable redistributable version of Panda3D targeted the end users. So I just have to put the game files inside and it’s ready for deployment.
I just wanted to share those ideas and recipes, so they can be helpful for someone. Everyone can build their own packages using those recipes.
For the next step I’m going to experiment with the latest Panda3D and RenderPipeline to make a package for it.
UPDATE: Everything was combined under the name “KITSUNETSUKI SDK” and moved into https://github.com/Yonnji/KITSUNETSUKI-SDK