From 4acbbaab06e0f5b2b3d5300f3afb8bacd645c7d2 Mon Sep 17 00:00:00 2001 From: Adam Shapiro Date: Wed, 1 Nov 2023 10:13:43 -0400 Subject: [PATCH] Update external project example to release 1.22.3. --- README.md | 14 +++++++------- examples/external_cmake_project/CMakeLists.txt | 8 ++++---- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index b1bf6514..48606a23 100644 --- a/README.md +++ b/README.md @@ -98,11 +98,11 @@ include(FetchContent) FetchContent_Declare( fusion_engine_client # Recommended: - URL https://github.com/PointOneNav/fusion-engine-client/archive/refs/tags/v1.16.0.zip - URL_HASH MD5=3d35c1c56e111d2e9a164cdbf7878228 - # Alternative: + URL https://github.com/PointOneNav/fusion-engine-client/archive/refs/tags/v1.22.3.zip + URL_HASH MD5=cfe1de319725822a1b825cd3421fb6b1 + # Alternatively: # GIT_REPOSITORY https://github.com/PointOneNav/fusion-engine-client.git - # GIT_TAG v1.16.0 + # GIT_TAG v1.22.3 ) set(P1_FE_BUILD_EXAMPLES OFF CACHE INTERNAL "") FetchContent_MakeAvailable(fusion_engine_client) @@ -114,7 +114,7 @@ target_link_libraries(example_app PUBLIC fusion_engine_client) ``` Note that we strongly recommend using a specific version of the library in your code by specifying a release zip file or -a git tag (e.g., `GIT_TAG v1.15.2`), and updating that as new versions are released. That way, you can be sure that your +a git tag (e.g., `GIT_TAG vA.B.C`), and updating that as new versions are released. That way, you can be sure that your code is always built with a known version of fusion-engine-client. If you prefer, however, you can tell CMake to track the latest changes by using `GIT_TAG master` instead. @@ -168,12 +168,12 @@ To use this library in an existing Bazel project, add the following to your proj git_repository( name = "fusion_engine_client", remote = "git@github.com:PointOneNav/fusion_engine_client.git", - tag = "v1.15.2", + tag = "v1.22.3", ) ``` Note that we strongly recommend using a specific version of the library in your code by specifying a git tag (e.g., -`tag = "v1.15.2"`), and updating that as new versions are released. That way, you can be sure that your code is always +`tag = "v1.22.3"`), and updating that as new versions are released. That way, you can be sure that your code is always built with a known version of fusion-engine-client. If you prefer, however, you can tell Bazel to track the latest changes by using `branch = "master"` instead. diff --git a/examples/external_cmake_project/CMakeLists.txt b/examples/external_cmake_project/CMakeLists.txt index e218a276..d2858f51 100644 --- a/examples/external_cmake_project/CMakeLists.txt +++ b/examples/external_cmake_project/CMakeLists.txt @@ -19,7 +19,7 @@ project(fusion_engine_usage_example C CXX) # Use FetchContent to import the fusion-engine-client C++ library using Git. # # Note that we always recommend using a specific version of the library in your -# code by specifying a release zip file or a git tag (e.g., `GIT_TAG v1.15.2`), +# code by specifying a release zip file or a git tag (e.g., `GIT_TAG vA.B.C`), # and updating that as new versions are released. That way, you can be sure that # your code is always built with a known version of fusion-engine-client. If you # prefer, however, you can set the GIT_TAG to track the latest changes by @@ -39,11 +39,11 @@ include(FetchContent) FetchContent_Declare( fusion_engine_client # Recommended: - URL https://github.com/PointOneNav/fusion-engine-client/archive/refs/tags/v1.16.0.zip - URL_HASH MD5=3d35c1c56e111d2e9a164cdbf7878228 + URL https://github.com/PointOneNav/fusion-engine-client/archive/refs/tags/v1.22.3.zip + URL_HASH MD5=cfe1de319725822a1b825cd3421fb6b1 # Or alternatively: # GIT_REPOSITORY https://github.com/PointOneNav/fusion-engine-client.git - # GIT_TAG v1.16.0 + # GIT_TAG v1.22.3 ) set(P1_FE_BUILD_EXAMPLES OFF CACHE INTERNAL "") FetchContent_MakeAvailable(fusion_engine_client)