Physics Simulation Forum

Hi,

I've made quite a few modifications to my local copy of Bullet because I'm working with my own very small implementation of the C/C++ runtime libraries. Problems I've addressed include:

* General CRT header file references (I only have one header file).
* Some code uses the CRT directly instead of using the Bullet versions (e.g. use of assert over btAssert).
* Placement new use requires <new> - I've added a custom one to Bullet so that it doesn't require that, without interfering with placement news in other libs.

Is there any interest in patches to remove Bullet of its dependence on all this? The solution would allow you to seamlessly swap in your own CRT or use the available system ones.

Cheers,
- Don

Regardless of the interest of the main developers, I would say you should defenitly post your patches here, in case other people are interested in a CRT-less bullet

How are you using this custom CRT?

A patch based on the recent trunk would be welcome indeed. We are planning some more work soon that touch large part of the Bullet repository, so we can consider your contribution too.

My game downloads/runs in a browser without any installs so I have my own, minimal CRT that doesn't require any DLLs or runtimes on the host machine. I'm getting Bullet to link with my CRT and its wrapped in a separate DLL that is downloaded on-demand (you get game visuals early without need for physics/collision).

I need to update to the latest Bullet as soon as possible so it would make sense for me to start my changes from scratch (knowing what I need to do) and submit some incremental patches. There's not much work required - it's mostly tedious search and replace.