Why is Bullet so hard to get setup :(

[Xecantur]

This is by far the most trouble I've had setting up a library I've ever had, I couldn't compile out of the box, had to go on a search and rescue mission, So by using cmake for the initial build for the libraries, then creating a new dir to house the new libs and the copied includes. I finally got it setup, got glut/opengl configured or so I had thought I'm currently trying to compile and run the ragdoll demo, got "undefined reference to glutmain" which makes no sense as I have linked both glew32 and glut32, and put the includes in the search path including the demos/opengl folder. I mean it seems like a well coded library just the deployment is seriously hampering my ability to learn on it. While I've not tried deploying the library on linux I'm sure its probably way easier than windows, I don't really understand why precompiled binaries don't exist I just want to learn on it.

I don't mean to complain so much but there is literally no documentation for people that have this much trouble (spent about 4 hours on google and bing). and seeing as how you guys are really the only free 3d physics engine out there(well worth using I've looked at ode but saw a lot of complaints other than the solver), (as well as having a former havok employee being the lead api designer) I would expect a well-oiled deployment across the boards(barring consoles and ios/android). if you must distribute source only please test all cases and not just on a working compile environment.

[Erwin Coumans]

???

Under Windows, with Visual Studio, building and running requires just a few clicks. Don't use cmake.

Download Bullet 2.81 source zipfile and unzip
Click on build/vs2010.bat
Open build\vs2010\0BulletSolution.sln
Hit F5

That's it. It cannot be simpler than that. No need to mess with anything else. No need to mess with glut, glew etc. It should just work.

Thanks,
Erwin