Commit f1322394 authored by Tim Übelhör's avatar Tim Übelhör
Browse files

Update README.md

parent 2a48068e
......@@ -25,23 +25,16 @@ findXXX.cmake files. Conan does not modify the CMAKE_PREFIX_PATH which would
disturb the catkin build process. Those targets can be found via find_package()
and later be linked with the built targets.
# Using cmake generator
This is not shown here but I found a way to make it work. Place the following
cide between catkin_package(...) and your first target defenition:
```cmake
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.13/conan.cmake"
"${CMAKE_BINARY_DIR}/conan.cmake")
endif()
include(${CMAKE_BINARY_DIR}/conan.cmake)
conan_cmake_run(CONANFILE conanfile.txt
BASIC_SETUP
BUILD missing)
```
# Using cmake_paths generator
Works much like cmake_find_package. Include the generated cmake file but don't
call the `conan_basic_setup`.
Then link the targets with ```${CONAN_LIBS}```.
# Using cmake generator
This is generally not advised, since catkin heavily depends on the
CMAKE_PREFIX_PATH which is modified by the `conan_basic_setup()`. It is
possible to build the project, if the conan related stuff is placed between
`catkin_package` and the targets, but the binaries won't find it's way to
the devel space.
# Requirements
Setup the following conan repositories:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment