"host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent built and so on. In this example, once the build of liba/0.1@user/testing finishes, as it is the only item in the first level, the second level can start, and it can build both libb/0.1@user/testing and libc/0 the third level, that contains libd/0.1@user/testing, because this package depends on them. Every item in each level has 4 elements: [ref, package_id, context, id]. At the moment the only necessary one

"host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent built and so on. In this example, once the build of liba/0.1@user/testing finishes, as it is the only item in the first level, the second level can start, and it can build both libb/0.1@user/testing and libc/0 the third level, that contains libd/0.1@user/testing, because this package depends on them. Every item in each level has 4 elements: [ref, package_id, context, id]. At the moment the only necessary one

"host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent built and so on. In this example, once the build of liba/0.1@user/testing finishes, as it is the only item in the first level, the second level can start, and it can build both libb/0.1@user/testing and libc/0 the third level, that contains libd/0.1@user/testing, because this package depends on them. Every item in each level has 4 elements: [ref, package_id, context, id]. At the moment the only necessary one

"host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent built and so on. In this example, once the build of liba/0.1@user/testing finishes, as it is the only item in the first level, the second level can start, and it can build both libb/0.1@user/testing and libc/0 the third level, that contains libd/0.1@user/testing, because this package depends on them. Every item in each level has 4 elements: [ref, package_id, context, id]. At the moment the only necessary one

build/{{settings.build_type}}/static {% endif %} [resdirs] {% for item in ["cmp1", "cmp2", "cmp3"] %} src/{{ item }}/resouces/{% if item != "cmp3" %}{{ settings.arch }}{% endif %} {% endfor %} You can used for your qbs builds. Add conanbuildinfo.qbs as a reference on the project level and a Depends item with the name conanbuildinfo: yourproject.qbs import qbs Project { references: ["conanbuildinfo separately, then also an aggregated information for all dependencies. This PremakeDeps wraps a single item of such information. Note the name of the package will be PremakeGen/0.1@/ as that

build/{{settings.build_type}}/static {% endif %} [resdirs] {% for item in ["cmp1", "cmp2", "cmp3"] %} src/{{ item }}/resouces/{% if item != "cmp3" %}{{ settings.arch }}{% endif %} {% endfor %} You can used for your qbs builds. Add conanbuildinfo.qbs as a reference on the project level and a Depends item with the name conanbuildinfo: yourproject.qbs import qbs Project { references: ["conanbuildinfo separately, then also an aggregated information for all dependencies. This PremakeDeps wraps a single item of such information. Note the name of the package will be PremakeGen/0.1@user/channel as that is

build/{{settings.build_type}}/static {% endif %} [resdirs] {% for item in ["cmp1", "cmp2", "cmp3"] %} src/{{ item }}/resouces/{% if item != "cmp3" %}{{ settings.arch }}{% endif %} {% endfor %} You can used for your qbs builds. Add conanbuildinfo.qbs as a reference on the project level and a Depends item with the name conanbuildinfo: yourproject.qbs import qbs Project { references: ["conanbuildinfo separately, then also an aggregated information for all dependencies. This PremakeDeps wraps a single item of such information. Note the name of the package will be PremakeGen/0.1@/ as that

recorded in ~/.conan/conan.conf. Install configurations: $ conan config install <item> # Copy the relevant contents from <item> to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf conan config get # Show the full conan.conf file $ conan config get log.level # Show the "level" item in the "log" section 2.2. Community-Created Format 9 Conan Documentation, Release 1.37.2 See conan "host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent

recorded in ~/.conan/conan.conf. Install configurations: $ conan config install <item> # Copy the relevant contents from <item> to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf conan config get # Show the full conan.conf file $ conan config get log.level # Show the "level" item in the "log" section 2.2. Community-Created Format 9 Conan Documentation, Release 1.38.0 See conan "host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent

recorded in ~/.conan/conan.conf. Install configurations: $ conan config install <item> # Copy the relevant contents from <item> to the user's ~/. ˓→conan directory. $ conan config install ./my_config.conf conan config get # Show the full conan.conf file $ conan config get log.level # Show the "level" item in the "log" section 2.2. Community-Created Format 9 Conan Documentation, Release 1.39.0 See conan "host", "2"]], # Fourth level libd [["app1/0.1@user/testing", "3bf2...5188", "host", "1"]] ] Every item in the outer list is a “level” in the graph, a set of packages that needs to be built, and are independent