Unhide cmake warning when Python3 Development is not found #565
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.
🦟 Bug fix
Unhides a cmake warning when python bindings will not be built
Summary
A cmake warning should be printed when python bindings will not be built (controlled by the logic around
add_subdirectory(python)
), but the warning was in a separate part of the code, allowing the warning to be missed if thePython3_Development_FOUND
variable changed in between.Since
GZ_BUILD_WARNING("")
only generates a cmake warning if invoked beforegz_configure_build
, I switched to usemessage(WARNING "")
in e464330.Also, the failed Ubuntu Noble CI build is expected because finding python is currently broken for all platforms, but only our Ubuntu Noble CI builds report cmake warnings. I believe finding python should be fixed once gazebosim/gz-msgs#479 is merged and released. I think it would be worth merging this so that our broken state is accurately reflected.
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.