Copter: Give better error in opendroneid build when DID_ENABLE=0. #26870
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on my report on discord:
Problem arises when:
--enable-opendroneid
DID_ENABLE
set to 0Should pre_arm_checks also be skipped or there should be a different error message like DID_ENABLE is not allowed to be 0 when compiled with --enable-opendroneid.
Currently one of the pre_arm_checks will fail but there's no indiciation of what exactly the problem is. A better error message or disabling pre arm checks might save time for users.
This PR adds a better error message to report that
DID_ENABLE
is not allowed to be 0 when compiled with--enable-opendroneid
.