Fix or disable specific warnings on various platforms #3501
Replies: 6 comments
-
With these settings:
I get 6340 warnings from bullet3 :-/ |
Beta Was this translation helpful? Give feedback.
-
Thanks tommimarkus, do you have a patch/pull request for this? Where do you put those lines in the CMakeLists.txt files? Is set_property(TARGET the same as SET_TARGET_PROPERTY(... ? |
Beta Was this translation helpful? Give feedback.
-
As far as I know |
Beta Was this translation helpful? Give feedback.
-
Do you have a patch that applies this to the existing Bullet CMakeLists.txt for all projects/libraries? Or alternatively, can you share your CMake build files that can build with those warnings enabled for all Bullet libraries? |
Beta Was this translation helpful? Give feedback.
-
Is there a non-cmake level way to suppressing warnings? Such as a default boolean on the method calls? Or are we not doing this due to performance reasons?
I get warnings when removing bodies that dont exist, and I seem to have to do it this way because I have objects being added and removed thus cluttering the "numBodies". Calling removeBodies on a range of indexes seems to work best for me, but I get a lot of warnings out of it. |
Beta Was this translation helpful? Give feedback.
-
@josiahls Your warning are run-time warnings in PyBullet. The other are C++ compile warnings, different. We could add some method to suppress warnings in PyBullet. |
Beta Was this translation helpful? Give feedback.
-
The Bullet code base generates many warnings on various compiles (and platforms). We should fix them or suppress them in cmake and premake.
Beta Was this translation helpful? Give feedback.
All reactions