Required Libraries

Post Reply
kmanuele
Posts: 5
Joined: Fri Aug 13, 2021 8:45 pm

Required Libraries

Post by kmanuele »

The 0_Bullet3Solution contains a lot of files, many are libs - some labeled Bullet3.., others Bullet.... (and one with Bullet2...)

I would like to extract the current, and necessary, libs into their own directory and build them there.

Can someone list the current set of libs for Bullet3 applications??

thanks

Kevin
User avatar
drleviathan
Posts: 741
Joined: Tue Sep 30, 2014 6:03 pm
Location: San Francisco

Re: Required Libraries

Post by drleviathan »

What do you really want to do? That is, you want to sort and organize the libraries for what purpose?

The Bullet source repository comes with a few optional extras but even some of the core Bullet libraries are optional depending on what kind of application you're building. For example libBulletSoftBody.a is only necessary if you're using the SoftBody features. So... what are you doing and why would you want to prune the clutter?
kmanuele
Posts: 5
Joined: Fri Aug 13, 2021 8:45 pm

Re: Required Libraries

Post by kmanuele »

I am/was confused by all the projects in 0_Bullet3Solution, some of which are libraries and others are apps. When I build the solution, all the libs and apps end up in the same \bin folder. Also, I prefer to organize my debug and release libs with same name but in different folders.

Related question: In the source repository, I see Bullet3Collision and BulletCollision. These are clearly different, but what is difference?

Sorry if I may be asking dumb questions.

Kevin
User avatar
drleviathan
Posts: 741
Joined: Tue Sep 30, 2014 6:03 pm
Location: San Francisco

Re: Required Libraries

Post by drleviathan »

Yeah, that is confusing. I think what happened was this (and someone please correct me if I'm wrong):

Bullet3 started as an effort to leverage GPU computation to do physics however progress on that front stalled. Meanwhile, Bullet2 was still being used and improved.. and eventually the C-API and PyBullet stuff Bullet v2.X was elevated to version v3.x. The old Bullet3 experiment remains in the codebase but is stale. You probably want to use BulletCollision library instead of Bullet3Collision.

Supporting evidence: If you compare the number of files in .../src/BulletCollision/ with .../src/Bullet3Collision/ you'll see more code in the former. If you examine the git commit history for the last several years you'll see that only build/maintenance changes have been going into the Bullet3* files but more more significant updates have been happening in Bullet*.
Post Reply