is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 Tutorial Conan Documentation, Release 2.3.2 (continued from previous page) } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 Tutorial Conan Documentation, Release 2.5.0 (continued from previous page) } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 Tutorial Conan Documentation, Release 2.4.1 (continued from previous page) } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 dd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 dd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 Tutorial Conan Documentation, Release 2.6.0 (continued from previous page) } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 Tutorial Conan Documentation, Release 2.7.1 (continued from previous page) } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 Tutorial Conan Documentation, Release 2.8.1 (continued from previous page) } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 dd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI

is not used. It is possible to evaluate new lockfiles for every different configuration, and then merge them: $ conan lock create . --lockfile-out=64.lock --lockfile-clean $ conan lock create . -s arch=x86 4127378fefdd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } $ conan lock merge --lockfile=32.lock --lockfile=64.lock --lockfile-out=conan.lock $ cat conan.lock { "version": "0 dd0%1675294635.6049662" ], "build_requires": [], "python_requires": [] } This multiple-clean + merge operation is not something that developers should do, only CI scripts, and for some ad- vanced CI