Skip to content
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

[xmlrpcpp] Fix build when gtest is not available #2177

Conversation

wxmerkt
Copy link
Contributor

@wxmerkt wxmerkt commented Aug 19, 2021

When gtest is not available, the target test_socket is not created by catkin_add_gtest (it provides a warning that gtest
was not found and does not add the test). Trying to set the target properties then leads to a configuration error. Making this block conditional on the existence of the target fixes the configuration error.

When gtest is not available, the target test_socket is not
created by catkin_add_gtest (it provides a warning that gtest
was not found and does not add the test). Trying to set the
target properties then leads to a configuration error. Making
this block conditional on the existence of the target fixes
the configuration error.
@jacobperron jacobperron merged commit 98545f8 into ros:noetic-devel Sep 1, 2021
jacobperron pushed a commit that referenced this pull request Sep 21, 2021
When gtest is not available, the target test_socket is not
created by catkin_add_gtest (it provides a warning that gtest
was not found and does not add the test). Trying to set the
target properties then leads to a configuration error. Making
this block conditional on the existence of the target fixes
the configuration error.
jacobperron pushed a commit that referenced this pull request Jan 6, 2022
When gtest is not available, the target test_socket is not
created by catkin_add_gtest (it provides a warning that gtest
was not found and does not add the test). Trying to set the
target properties then leads to a configuration error. Making
this block conditional on the existence of the target fixes
the configuration error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants