These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, 11.24. Custom integrations 169 conan Documentation, package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, 178 Chapter 12. Integrations conan Documentation, Release package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, 180 Chapter 12. Integrations conan Documentation, Release package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades package folder. Hence calling package() twice, while having no side effects, is wasting a couple of cycles, since source code is already copied in the first invocation of package() and the install step will helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan

These generators have to be discovered (search), but they have many advantages: much faster release cycles, independent from the main conan codebase, can be versioned, so backward compatibility and upgrades helper to retrieve the number of cores, so it can be used in concurrent builds • Feature: Detects cycles in the dependency graph, and raise error instead of exhausting recursion limits • Feature: Conan