broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build

broken. • Only documented features in https://docs.conan.io are considered part of the public interface of Conan. Private implementation details, and everything not included in the documentation is subject extension points, named “plugins” have been added, to provide advanced and typically orthogonal function- ality to what the Conan recipes implement. These plugins can be shared, managed and installed via this case, as our project uses CMake as the build system, we call to cmake_layout(). Calling this function will set the expected locations for a CMake project. • The generate() method prepares the build