-
Notifications
You must be signed in to change notification settings - Fork 280
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
configure order for dignostics #264
Comments
i realize the logs look awful on github, compilation errors occur around 23%, look for "compilation terminated." |
Also this is using latest catkin master branch |
Note this is also strange because calling make without -j8 does not give that error (gives another one due to bug in cmakeLists.txt) |
This looks like a missing target dependency in CMake. The target which compiles the file match_no_analyze_analyzer.cpp should have an explicit dependency on the diagnostic_msgs message generation target (diagnostic_msgs_gencpp). The reason is that CMake will build those targets in parallel as it does not know that the compilation of the cpp file include a to-be-generated-header. |
ok, will open ticket on diagnostic |
Hi,
trying to build a groovy underlay with diagnostic packages, I got a strange error. Maybe this needs to be fixed in the diagnostics 'stack', since I get no similar behavior from other stacks.. However since the configure step seems to have orderings right, this might also be a catkin bug. Note how early "Scanning dependencies of target test_diagnostic_aggregator" appears. Below are also the package.xmls of diagnostics and test_diagnostc_aggregator I have (should be latest from groovy-devel). Maybe diagnostics meta-package misses build_depend tags (in comparison to other meta-packages), but I think catkin should probably work with it as it is.
diagnostics package xml
test_diagnostic_aggregator/package.xml
The text was updated successfully, but these errors were encountered: