to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake [options] copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] cmake (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only (but focused in) for C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the [options] section in conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only for (but focused on) C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the [options] section in conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable [generators] copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only for (but focused on) C/C++

to a default value in the recipe. For example, one package can define that its default linkage is static, and this is the linkage that should be used if consumers don’t specify otherwise. Note: You can we can modify the previous example to use dynamic linkage instead of the default one, which was static, by editing the [options] section in conanfile.txt: [requires] Poco/1.9.0@pocoproject/stable (continues copying the resulting executables to your bin folder, or for copying assets, images, sounds, test static files, etc. Conan is a generic solution for package management, not only for (but focused on) C/C++