Skip to content

Use ament_vendor for zmqpp library#1634

Merged
HansRobo merged 3 commits intomasterfrom
fix/zmqpp
Jul 7, 2025
Merged

Use ament_vendor for zmqpp library#1634
HansRobo merged 3 commits intomasterfrom
fix/zmqpp

Conversation

@f0reachARR
Copy link
Copy Markdown
Contributor

Description

Abstract

Use ament_vendor for zmqpp library, instead of ExternalProject.

Details

This section is same as autowarefoundation/zmqpp_vendor#9

References

Destructive Changes

  • Install directory of zmqpp is changed

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jun 23, 2025

Checklist for reviewers ☑️

All references to "You" in the following text refer to the code reviewer.

  • Is this pull request written in a way that is easy to read from a third-party perspective?
  • Is there sufficient information (background, purpose, specification, algorithm description, list of disruptive changes, and migration guide) in the description of this pull request?
  • If this pull request contains a destructive change, does this pull request contain the migration guide?
  • Labels of this pull request are valid?
  • All unit tests/integration tests are included in this pull request? If you think adding test cases is unnecessary, please describe why and cross out this line.
  • The documentation for this pull request is enough? If you think adding documents for this pull request is unnecessary, please describe why and cross out this line.

@f0reachARR f0reachARR marked this pull request as ready for review June 23, 2025 16:30
@github-actions
Copy link
Copy Markdown

Failure optional scenarios

Note

This is an experimental check and does not block merging the pull-request.
But, please be aware that this may indicate a regression.

scenario failed: execution_time_test
      <failure type="SimulationFailure" message="CustomCommandAction typed &quot;exitFailure&quot; was triggered by the named Conditions {&quot;update time checker&quot;, &quot;avoid startup&quot;}: {&quot;update time checker&quot;: Is the /simulation/interpreter/execution_time/update (= 0.005232999999999999804489725364) is greaterThan 0.005?}, {&quot;avoid startup&quot;: Is the simulation time (= 5.499999999999988453680543898372) is greaterThan 1.000000000000000000000000000000?}" />

@HansRobo HansRobo self-requested a review July 7, 2025 06:26
@HansRobo HansRobo added the bump patch If this pull request merged, bump patch version of the scenario_simulator_v2 label Jul 7, 2025
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Jul 7, 2025

Copy link
Copy Markdown
Member

@HansRobo HansRobo left a comment

Choose a reason for hiding this comment

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

LGTM. I also checked the build include this on Autoware Evaluator.

@HansRobo HansRobo merged commit 7384223 into master Jul 7, 2025
@github-actions github-actions bot deleted the fix/zmqpp branch July 7, 2025 10:06
@xmfcx
Copy link
Copy Markdown
Contributor

xmfcx commented Dec 18, 2025

@f0reachARR @HansRobo

Use ament_vendor for zmqpp library, instead of ExternalProject.

Could you explain why you've added ament_cmake_vendor_package dependency with this PR?

ament_cmake_vendor_package depends on the deprecated vcstool and Prevents us from going ahead with 📣 Switching from vcstool to vcs2l #6645.

I'm going to create a PR to switch to ExternalProject and remove the ament_cmake_vendor_package dependency.

This way the users can keep using the modern tooling.

Related:

@xmfcx
Copy link
Copy Markdown
Contributor

xmfcx commented Dec 18, 2025

Actually, since this PR comes with a destructive change, I don't have the courage to revert this.

We should instead update the build farm version with these changes and use this vendor package from the build farm with rosdep.

Tracked issue:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump patch If this pull request merged, bump patch version of the scenario_simulator_v2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants