We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
seems useful after: ros-perception/image_common#31
(plus, there were already problems between 0.3 and 0.5)
There is an open issue upstream: https://code.google.com/p/yaml-cpp/issues/detail?id=127
Even though there is some CMake code here: https://code.google.com/p/yaml-cpp/source/browse/
Should we comply to their notation ? YAML_CPP_INCLUDE_DIR and not YAML_CPP_INCLUDE_DIRS
The text was updated successfully, but these errors were encountered:
Proof of concept that works for me here: #31
Sorry, something went wrong.
Ok, I'll have a look tomorrow. Sorry for the delay, this got lost in my inbox noise.
We can have a FindYAMLCpp.cmake, but we should fix the logic so it actually makes sense first.
FindYAMLCpp.cmake
No branches or pull requests
seems useful after:
ros-perception/image_common#31
(plus, there were already problems between 0.3 and 0.5)
There is an open issue upstream:
https://code.google.com/p/yaml-cpp/issues/detail?id=127
Even though there is some CMake code here:
https://code.google.com/p/yaml-cpp/source/browse/
Should we comply to their notation ? YAML_CPP_INCLUDE_DIR and not YAML_CPP_INCLUDE_DIRS
The text was updated successfully, but these errors were encountered: