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

Fail to find a component if one of its external dependencies is missing #1223

Merged
merged 12 commits into from
Jan 14, 2019

Conversation

mxgrey
Copy link
Member

@mxgrey mxgrey commented Jan 11, 2019

This addresses the conversation at the bottom of #1222: If an external dependency of a component is missing, then the component will be declared as "not found", which should create a configuration error when that component is required.


Before creating a pull request

  • Document new methods and classes
  • Format new code files using clang-format

Before merging a pull request

  • Set version target by selecting a milestone on the right side
  • Summarize this change in CHANGELOG.md
  • Add unit test(s) for this change

@mxgrey
Copy link
Member Author

mxgrey commented Jan 11, 2019

Note that this was committed on top of #1222, so that one should be reviewed and merged before this one.

@jslee02 jslee02 added this to the DART 6.7.1 milestone Jan 11, 2019
jslee02
jslee02 previously approved these changes Jan 14, 2019
Copy link
Member

@jslee02 jslee02 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This solution looks much cleaner than my suggestion in #1209! Besides the nitpick, looks good to go!

@jslee02 jslee02 merged commit eaa7440 into release-6.7 Jan 14, 2019
@jslee02 jslee02 deleted the grey/fail_config_when_dep_missing branch January 14, 2019 17:37
mxgrey added a commit that referenced this pull request Jan 16, 2019
jslee02 pushed a commit that referenced this pull request Jan 17, 2019
There's a case where the changes in #1223 fail if dependent components are requested. For example, if you ask for

```
find_package(DART COMPONENTS utils utils-urdf)
```

then the build system can get confused about whether or not the component and its dependencies were properly found. We fix that in this PR by moving the location where the `TRUE` assumption is made.
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