Commands

There is no “compatible with 2.X” commands introduced in Conan 1.X. You will need to adapt to the new commands once you migrate to Conan 2.0

Most common commands overview

conan install

Almost the same command, the major change is the way to specify (or compete if not defined) the fields of the reference. Remember that in Conan 1.X you have to specify the build profile or activate the conf core:default_build_profile=default.

$ conan install . [--name=mylib] [--version=1.0] [-pr:b=build_profile] [-pr:h=host_profile]

conan create

Same changes as conan install:

$ conan create . [--name=mylib] [--version=1.0] [-pr:b=build_profile] [-pr:h=host_profile]

conan graph info

This is the substitute of the old “conan info”. The syntax is very similar to conan install and conan create

$ conan graph info . [--name=mylib] [--version=1.0] [-pr:b=build_profile] [-pr:h=host_profile]

conan search

The conan search will search, by default, in all the remotes (not in the local cache):

$ conan search "zlib*"

myremote:
  zlib
    zlib/1.2.11
conancenter:
  zlib-ng
    zlib-ng/2.0.2
    zlib-ng/2.0.5
    zlib-ng/2.0.6
  zlib
    zlib/1.2.11
    zlib/1.2.8

If you want to explore the local cache there is a command conan list recipes <pattern>.

Unified patterns in command arguments

The arguments in Conan 1.X where we specified recipe names require now a valid reference pattern. A valid reference pattern contains the * character or at least the name/version part of a reference (name/version@user/channel).

There are some examples:

The --build argument when referring to a package:

From:

 conan install . --build zlib

To:

 conan install . --build zlib*
 conan install . --build zlib/1.2.11
 conan install . --build zlib/1.*

The --options and --settings arguments when used scoped:

From:

 conan install . -s zlib:arch=x86 -o zlib:shared=True

To:

 conan install . -s zlib*:arch=x86 -o zlib*:shared=True
 conan install . -s zlib/1.2.11@user/channel:arch=x86 -o zlib/1.2.11:shared=True

Removed “conan package”

The conan package command has been removed. If you are developing a recipe and want to test that the package method is correct, we recommend using the conan export-pkg . instead and exploring the package folder in the cache to check if everything is ok.

Removed “conan copy”

Do not use the conan copy command to change user/channel. Packages will be immutable, and this command will disappear in 2.0. Package promotions are generally done on the server-side, copying packages from one server repository to another repository.

Custom commands

You can build custom commands on top of the Conan Python API. WIP documentation.