Skip to content

Commit

Permalink
[workspace] Upgrade lcm to latest release v1.5.1
Browse files Browse the repository at this point in the history
  • Loading branch information
nicolecheetham committed Jan 6, 2025
1 parent 61c5e88 commit 7fa8be5
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 6 deletions.
4 changes: 2 additions & 2 deletions tools/workspace/lcm/lcm-config-version.cmake
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
set(PACKAGE_VERSION "1.5.0")
set(PACKAGE_COMPAT_VERSION "1.5.0")
set(PACKAGE_VERSION "1.5.1")
set(PACKAGE_COMPAT_VERSION "1.5.1")

if(PACKAGE_VERSION VERSION_LESS PACKAGE_FIND_VERSION)
set(PACKAGE_VERSION_COMPATIBLE FALSE)
Expand Down
2 changes: 1 addition & 1 deletion tools/workspace/lcm/lcm-config.cmake
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ unset(_targetsDefined)
unset(_targetsNotDefined)
unset(_expectedTargets)

set(lcm_VERSION "1.5.0")
set(lcm_VERSION "1.5.1")

add_library(lcm::lcm-coretypes INTERFACE IMPORTED)
set_target_properties(lcm::lcm-coretypes PROPERTIES
Expand Down
8 changes: 5 additions & 3 deletions tools/workspace/lcm/repository.bzl
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,12 @@ def lcm_repository(
repository = "lcm-proj/lcm",
upgrade_advice = """
When updating, the version numbers within the two lcm-*.cmake files in
this directory must also be updated to match the new version.
this directory must also be updated to match the new version. Moreover,
lcm needs its own pull request separate from the rest of the monthly
upgrades.
""",
commit = "v1.5.0",
sha256 = "590a7d996daa3d33a7f3094e4054c35799a3d7a4780d732be78971323e730eeb", # noqa
commit = "v1.5.1",
sha256 = "40ba0b7fb7c9ad06d05e06b4787d743cf11be30eb4f1a03abf4a92641c5b1203", # noqa
build_file = ":package.BUILD.bazel",
mirrors = mirrors,
)

0 comments on commit 7fa8be5

Please sign in to comment.