Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I have partially worked this out:

Disable googletest warnings by disabling testing

catkin config -DCATKIN_ENABLE_TESTING=0

This is obviously no good if you actually want testing enabled. Unfortunately I found that upgrading google test to the latest (final) release from a PPA didn't fix these warnings. They are fixed upstream, but googletest don't do releases anymore, so you have to manually install from github master branch. could work but don't really want to recommend this to all users.

Disable PCL warnings (and indeed all 3rd party warnings - maybe not desirable?) by modifying CMakeLists.txt like:

include_directories(
 SYSTEM # suppress warnings from 3rd party libs that we can't control
 ${catkin_INCLUDE_DIRS}
)

I have partially worked this out:

Disable googletest warnings by disabling testing

catkin config -DCATKIN_ENABLE_TESTING=0

This is obviously no good if you actually want testing enabled. Unfortunately I found that upgrading google test to the latest (final) release from a PPA didn't fix these warnings. They are fixed upstream, but googletest don't do releases anymore, so you have to manually install from github master branch. alternatively could manually edit the CMakeLists.txt under /usr/src/googletest which some people have reported success with. either could work but don't really want to recommend this to all users.

Disable PCL warnings (and indeed all 3rd party warnings - maybe not desirable?) by modifying CMakeLists.txt like:

include_directories(
 SYSTEM # suppress warnings from 3rd party libs that we can't control
 ${catkin_INCLUDE_DIRS}
)