-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build against bullet double precision library #191
Comments
Hello there, I am not a maintainer or anything, but I just wanted to ask you if there were any noticeable benefits to using double precision bullet, (like when playing) as well as how to build with double precision? |
The main reason was that openmw require bullet library with double precision, there was collision issue that they fixed that way. I think you will learn more with the openmw pull request: |
Hello again, thanks for the information, but when I try to build (with your changes) it gives me this error (with bullet from homebrew and
Am I supposed to have this error, or am I using a wrong version of bullet or smth. Thanks again |
Also, when I do the casts and it compiles, it gives these linker errors:
commit here |
When I say logs, I mean FULL LOGS, even the last failing build commands :) From what I see you builded against a double precision bullet, but at linking step you seems to miss a -lBulletWorldImporter or somthing in the linking command. You may require this patch and rebuild your bullet library with it to have the library exported in the cmake config file: It's strange, seeing the log I required this patch only for stuntrally, not for vdrift... Or did I do vdrift after stuntrally and didn't encounter the problem, dunno ? |
Hi,
This follow up my trouble to get vdrift and stuntrally to build with a double precision bullet library.
Here is the patch that fixes it:
https://svnweb.mageia.org/packages/cauldron/vdrift/current/SOURCES/vdrift-2014-10-20-bullet-double.patch?revision=1919674&view=markup
Best regards
The text was updated successfully, but these errors were encountered: