. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 345 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 348 17.12 How to manage shared libraries . can be done manually. Set up configurations: $ conan config init # Initialize Conan configuration files. If some are already␣ ˓→present, missing files only are # created Set configuration values: $ conan config set

.= $ conan config set log.level=10 $ conan config set log.print_run_commands=False # Make conan less verbose Inspect configurations: $ conan config home #

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 362 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 365 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 360 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 363 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenams and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 359 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 362 17.12 How to manage shared libraries deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 370 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 373 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 368 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 371 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account

. . . . . . . . . . . . . . . . . . . . . . 370 17.11 How to create and share a custom generator with generator packages . . . . . . . . . . . . . . . . . . 373 17.12 How to manage shared libraries . deps_user_info, these have been removed in 2.0. Note: If you don’t need to customize anything in a generator you can specify it in the generators attribute and skip using the generate() method for that: from New properties model Migrating legacy cpp_info attributes to set_property() Migrating from .names, .filenames and .build_modules to set_property() is easy, but there are some details to take into account