built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported the Conan Package layout. • Documentation for all conanfile.py available methods. • Importing resource files in the generate() method • Conditional generators in configure() 4.1.5 How to cross-compile

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]

built a simple CMake project that depended on the zlib library and learned about tool_requires, a special type of requirements for build-tools like CMake. In both cases, we did not specify anywhere that architecture on macOS you can raise the ConanInvalid- Configuration exception to make Conan return with a special error code. This will indicate that the configuration used for settings or options is not supported class MyProject(ConanFile): ... def generate(self): # Copy all resources from the dependency's resource directory # to the "assets" folder in the source directory of your project dep = self.dependencies["dep_name"]