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

Fixes policy CMP0135 warning for CMake >= 3.24 #35

Merged
merged 12 commits into from
Sep 9, 2022

Conversation

Crola1702
Copy link
Contributor

@Crola1702 Crola1702 commented Sep 8, 2022

Warning fix
Signed-off-by: Cristóbal Arroyo [email protected]

This warning started appearing on new machines (windows-container-bd99e2f0 and others). It’s caused by a new CMake version (3.24) that expects this policy to be set.

Solution with this PR changes:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

This last windows build wasn't run right (probably the agent didn't had the CMake3.24 version)

Copy link
Contributor

@clalancette clalancette left a comment

Choose a reason for hiding this comment

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

This seems like a strange file to set the policy in. That is, the problem is in the main CMakeLists.txt, where we actually call ExternalProject_Add, but this is the cmake file that we export to downstream consumers. So I don't quite understand why it is in here; can you explain more?

@Crola1702
Copy link
Contributor Author

Crola1702 commented Sep 9, 2022

This seems like a strange file to set the policy in. That is, the problem is in the main CMakeLists.txt, where we actually call ExternalProject_Add, but this is the cmake file that we export to downstream consumers. So I don't quite understand why it is in here; can you explain more?

Yes. I was trying to apply the solution we used in osrf_testing_tools_cpp (osrf/osrf_testing_tools_cpp#71) by setting the policy in cmake.in

New builds:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

Now it's working fine on all three builds.

@Crola1702 Crola1702 marked this pull request as ready for review September 9, 2022 17:24
Copy link

@Blast545 Blast545 left a comment

Choose a reason for hiding this comment

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

LGTM

@Crola1702 Crola1702 merged commit 5565d5b into rolling Sep 9, 2022
@delete-merged-branch delete-merged-branch bot deleted the Crola1702/fix-cmp0135-policy-warning branch September 9, 2022 19:02
@MichaelOrlov
Copy link

https://github.com/Mergifyio backport humble

@mergify
Copy link

mergify bot commented Nov 23, 2022

backport humble

❌ Command disallowed due to command restrictions in the Mergify configuration.

  • sender-permission>=write

@MichaelOrlov
Copy link

@cottsay @clalancette Could you please backport this PR to the Humble?
It turns out that Mergify refuses to create PR since I don't have write permissions to this repo.
Without this PR our CI throwing warning and reporting that build unstable due to the new warnings.
One of the warnings from https://ci.ros2.org/job/ci_windows/18281/

@Crola1702
Copy link
Contributor Author

https://github.com/Mergifyio backport humble

mergify bot pushed a commit that referenced this pull request Nov 23, 2022
* Sets CMP0135 policy

Signed-off-by: Crola1702 <[email protected]>
(cherry picked from commit 5565d5b)
@mergify
Copy link

mergify bot commented Nov 23, 2022

backport humble

✅ Backports have been created

@Crola1702
Copy link
Contributor Author

Could you please backport this PR to the Humble?

@MichaelOrlov check #41

@MichaelOrlov
Copy link

@Crola1702 Thanks, looking forward to be merged.

clalancette pushed a commit that referenced this pull request Nov 28, 2022
* Sets CMP0135 policy

Signed-off-by: Crola1702 <[email protected]>
(cherry picked from commit 5565d5b)

Co-authored-by: Cristóbal Arroyo <[email protected]>
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.

4 participants