Common Package Specification (CPS) in Practice: A Full Round Trip Implementation in Conan C++ Package Manager"name": "zlib", "version": "1.3.1", "configurations": ["release"], "default_components": ["zlib"], "components": { "zlib": { "type": "archive", "includes": ["@prefix@/include"] Unobtrusive …", "website": "https://zlib.net", "configurations": ["release"], "default_components": ["zlib"], "components": { "zlib": { "type": "archive", "includes": ["C:/Users/Diego/.co Unobtrusive …", "website": "https://zlib.net", "configurations": ["release"], "default_components": ["zlib"], "components": { "zlib": { "type": "archive", "includes": ["C:/Users/Diego/.co0 码力 | 66 页 | 1.76 MB | 6 月前3
Conan 2.0 Documentationconfiguration values to consumers • Propagating environment information to consumers • Define components for Conan packages that provide multiple libraries Let’s see some of those in action. First, clone corresponding example. 4.2. Creating packages 77 Conan Documentation, Release 2.0.17 Define components for Conan packages that provide multiple libraries There are cases in which a Conan package may information for each of those libraries using the components attribute from the CppInfo object. To know more about this use case, please check the components example in the examples section. Read more •0 码力 | 652 页 | 4.00 MB | 1 年前3
Conan 2.1 Documentationinformation to consumers 76 Chapter 4. Tutorial Conan Documentation, Release 2.1.0 • Define components for Conan packages that provide multiple libraries Let’s see some of those in action. First, clone the ConanFile. To know more about this use case, please check the corresponding example. Define components for Conan packages that provide multiple libraries There are cases in which a Conan package may information for each of those libraries using the components attribute from the CppInfo object. To know more about this use case, please check the components example in the examples section. See also: •0 码力 | 694 页 | 4.13 MB | 1 年前3
Conan 1 Documentationprevious page) self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: package_info(self): ... for generator in ["cmake_find_package", "cmake_find_package_multi"]: self.cpp_info.components["main"].build_modules[generator].append(os.path. �→join("lib", "cmake", "pybind11", "pybind11Common "pybind11Common.cmake")]) ... Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components sup- port, so for example: def package_info(self):0 码力 | 975 页 | 8.75 MB | 1 年前3
Conan 1.63 Documentationbindirs => ["bin"] self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: package_info(self): ... for generator in ["cmake_find_package", "cmake_find_package_multi"]: self.cpp_info.components["main"].build_modules[generator].append(os.path. ˓→join("lib", "cmake", "pybind11", "pybind11Common "pybind11Common.cmake")]) ... Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components support, so for example: def package_info(self):0 码力 | 995 页 | 7.54 MB | 1 年前3
Conan 1.62 Documentationbindirs => ["bin"] self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: package_info(self): ... for generator in ["cmake_find_package", "cmake_find_package_multi"]: self.cpp_info.components["main"].build_modules[generator].append(os.path. ˓→join("lib", "cmake", "pybind11", "pybind11Common "pybind11Common.cmake")]) ... Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components support, so for example: def package_info(self):0 码力 | 993 页 | 7.53 MB | 1 年前3
Conan 1.64 Documentationbindirs => ["bin"] self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: package_info(self): ... for generator in ["cmake_find_package", "cmake_find_package_multi"]: self.cpp_info.components["main"].build_modules[generator].append(os.path. ˓→join("lib", "cmake", "pybind11", "pybind11Common "pybind11Common.cmake")]) ... Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components support, so for example: def package_info(self):0 码力 | 999 页 | 7.54 MB | 1 年前3
Conan 1.56 Documentationbindirs => ["bin"] self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: CMakeDeps properties reference. Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components support, so for example: def package_info(self): package_info(self): ... self.cpp_info.components["mycomponent"].names["cmake_find_package"] = "mycomponent- ˓→name" self.cpp_info.components["mycomponent"].names["cmake_find_package_multi"] = ˓→"mycomponent-name"0 码力 | 963 页 | 7.67 MB | 1 年前3
Conan 1.55 Documentationbindirs => ["bin"] self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: CMakeDeps properties reference. Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components support, so for example: def package_info(self): package_info(self): ... self.cpp_info.components["mycomponent"].names["cmake_find_package"] = "mycomponent- ˓→name" self.cpp_info.components["mycomponent"].names["cmake_find_package_multi"] = ˓→"mycomponent-name"0 码力 | 963 页 | 7.67 MB | 1 年前3
Conan 1.53 Documentationbindirs => ["bin"] self.cpp_info.builddirs => [] self.cpp_info.frameworkdirs => [] If you declare components, the defaults are the same, so you only need to change the defaults if they are not correct. Note: CMakeDeps properties reference. Migrating components information As we said, all these properties but cmake_file_name and cmake_module_file_name have components support, so for example: def package_info(self): package_info(self): ... self.cpp_info.components["mycomponent"].names["cmake_find_package"] = "mycomponent- ˓→name" self.cpp_info.components["mycomponent"].names["cmake_find_package_multi"] = ˓→"mycomponent-name"0 码力 | 953 页 | 7.64 MB | 1 年前3
共 130 条
- 1
- 2
- 3
- 4
- 5
- 6
- 13













