From 00b4c020b45e91f6f7160f58858107b82429ee6f Mon Sep 17 00:00:00 2001 From: czoido Date: Tue, 23 Feb 2021 15:18:36 +0100 Subject: [PATCH] set v0.16 --- README.md | 4 ++-- conan.cmake | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index daed7473..de83a0d7 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ The branches in this repo are: You probably want to use a tagged release to ensure controlled upgrades. You can just clone or grab the *conan.cmake* file and put in in your project. -Or it can be used in this way. Note the ``v0.15`` tag in the URL, change it to point to your desired release: +Or it can be used in this way. Note the ``v0.16`` tag in the URL, change it to point to your desired release: ```cmake @@ -29,7 +29,7 @@ add_definitions("-std=c++11") if(NOT EXISTS "${CMAKE_BINARY_DIR}/conan.cmake") message(STATUS "Downloading conan.cmake from https://github.com/conan-io/cmake-conan") - file(DOWNLOAD "https://raw.githubusercontent.com/conan-io/cmake-conan/v0.15/conan.cmake" + file(DOWNLOAD "https://raw.githubusercontent.com/conan-io/cmake-conan/v0.16/conan.cmake" "${CMAKE_BINARY_DIR}/conan.cmake" TLS_VERIFY ON) endif() diff --git a/conan.cmake b/conan.cmake index ca97b3f6..321e95cc 100644 --- a/conan.cmake +++ b/conan.cmake @@ -33,7 +33,7 @@ # but it is only necessary on the end-user side. It is not necessary to create conan # packages, in fact it shouldn't be use for that. Check the project documentation. -# version: 0.16.0-dev +# version: 0.16.0 include(CMakeParseArguments)