Integrations

This topical list of build systems, IDEs, and CI platforms provides information on how conan packages can be consumed, created, and continuously deployed/tested with each, as applicable.

• CMake
  • cmake generator
  • cmake_multi generator
  • cmake_paths generator
  • cmake_find_package generator
  • Build automation
  • Find Packages
• Autotools: configure/make
• Visual Studio
  • With CMake
  • With visual_studio generator
  • Calling Visual Studio compiler
  • Build an existing Visual Studio project
  • Toolsets
• Apple/Xcode
  • With CMake
  • With the xcode generator
• Compilers on command line
• Android Studio
• CLion
  • Using packages in a CLion project
  • Creating conan packages in a CLion project
• Ninja, NMake, Borland
• pkg-config and .pc files
  • Approach 1: Import and patch the prefix in the .pc files
  • Approach 2: Prepare and package .pc files before package them
  • Approach 3: Use --define-prefix
  • Approach 4: Use PKG_CONFIG_$PACKAGE_$VARIABLE
  • Approach 5: Use the pkg_config generator
• Boost Build
• B2 (Boost Build)
• QMake
  • Example
• Premake
  • Example
• Make
  • Example
• qbs
• Meson Build
• SCons
• Docker
• Git
  • Temporary files
  • Package creators
• Jenkins
  • Artifactory and Jenkins integration
• Travis Ci
  • Building and testing your project
  • Creating, testing and uploading conan binary packages
• Appveyor
  • Building and testing your project
  • Creating, testing and uploading conan binary packages
• Gitlab
  • Building and testing your project
  • Creating, testing and uploading conan binary packages
• Circle CI
  • Building and testing your project
  • Creating, testing and uploading conan package binaries
• YouCompleteMe (vim)
• Custom integrations
  • Use the JSON generator
  • Use the text generator
  • Use conan data model (conanfile.py)
  • Create your own generator
• Linting conanfile.py
• Microsoft’s Azure DevOps (TFS, VSTS)
  • Configuring DevOps Azure to use Artifactory with Conan
  • Steps to follow