Documentation for components and cmake_find_package generator

creating_packages/package_information.rst

@@ -106,20 +106,30 @@ Declaration of requires from other packages is also allowed:
         ...
         requires = "zlib/1.2.11", "openssl/1.1.1g"
 
-    def package_info(self):
-        self.cpp_info.components["comp1"].requires = ["zlib::zlib"]             # Depends on all components in zlib package
-        self.cpp_info.components["comp2"].requires = ["comp1", "openssl::ssl"]  # Depends on ssl component in openssl package
+        def package_info(self):
+            self.cpp_info.components["comp1"].requires = ["zlib::zlib"]  # Depends on all components in zlib package
+            self.cpp_info.components["comp2"].requires = ["comp1", "openssl::ssl"]  # Depends on ssl component in openssl package
 
 By default, components **won't link against any other package required by the recipe**. The requires list has to be **populated explicitly**
 with the list of components from other packages to use: it can be the full requirement (``zlib::zlib``) or a single component
 (``openssl::ssl``).
 
 .. important::
 
-    Components information is still not available from the generators' side. We are planning to complete this feature in next releases.
+    The information of components is aggregated to the *global* ``cpp_info`` scope and the usage of components should be transparent.
+
+Consumers can get this information via ``self.deps_cpp_info`` as usual and use it in the ``build()`` method of any dependent recipe:
+
+.. code-block:: python
+
+    class PocoTimerConan(ConanFile):
+        ...
+        requires = "zlib/1.2.11", "openssl/1.0.2u"
+        ...
 
-    Currently, the information of components is not lost but aggregated to the *global* scope and the usage of components should be
-    transparent right now.
+        def build(self):
+            # Get the include directories of the SSL component of openssl package
+            self.deps_cpp_info["openssl"].components["ssl"].include_paths
 
 .. seealso::
 

reference/conanfile/attributes.rst

@@ -991,6 +991,9 @@ absolute paths, and ``name`` and ``version`` attributes:
 +-----------------------------------------------+---------------------------------------------------------------------+
 | self.deps_cpp_info["dep"].version             | Get the version of the "dep" package                                |
 +-----------------------------------------------+---------------------------------------------------------------------+
+| self.deps_cpp_info["dep"].components          | | **[Experimental]** Dictionary with different components a package |
+|                                               | | may have: libraries, executables...                               |
++-----------------------------------------------+---------------------------------------------------------------------+
 
 To get a list of all the dependency names from ```deps_cpp_info```, you can call the `deps` member:
 
@@ -1023,7 +1026,6 @@ root folder of the package:
             # Get the sharedlinkflags property from OpenSSL package
             self.deps_cpp_info["openssl"].sharedlinkflags
 
-
 .. _env_info_attributes_reference:
 
 env_info

reference/generators/cmake_find_package.rst

@@ -55,8 +55,8 @@ utilities exported by the package available for consumers just by setting `find_
 Moreover, this also adjusts `CMAKE_MODULE_PATH` and `CMAKE_PREFIX_PATH` to the values declared by the package in ``cpp_info.buildirs``, so
 modules in those directories can be found.
 
-Target in Find<PKG-NAME>.cmake
-------------------------------
+Targets in Find<PKG-NAME>.cmake
+-------------------------------
 
 A target named ``<PKG-NAME>::<PKG-NAME>`` target is generated with the following properties adjusted:
 
@@ -67,3 +67,18 @@ A target named ``<PKG-NAME>::<PKG-NAME>`` target is generated with the following
 The targets are transitive. So, if your project depends on a packages ``A`` and ``B``, and at the same time
 ``A`` depends on ``C``, the ``A`` target will contain automatically the properties of the ``C`` dependency, so
 in your `CMakeLists.txt` file you only need to ``find_package(A)`` and ``find_package(B)``.
+
+Components
+++++++++++
+
+If a recipe uses components, the targets generated will be ``<PKG-NAME>::<COMP-NAME>`` with the following properties adjusted:
+
+- ``INTERFACE_INCLUDE_DIRECTORIES``: Containing all the include directories of the component.
+- ``INTERFACE_LINK_DIRECTORIES``: Containing all the lib directories of the component.
+- ``INTERFACE_LINK_LIBRARIES``: Containing the targets to link the component to (includes component's libraries and dependencies).
+- ``INTERFACE_COMPILE_DEFINITIONS``: Containing the definitions of the component.
+- ``INTERFACE_COMPILE_OPTIONS``: Containing the compile options of the component.
+
+Moreover, a global target ``<PKG-NAME>::<PKG-NAME>`` will be declared with the following properties adjusted:
+
+- ``INTERFACE_LINK_LIBRARIES``: Containing all the component targets to link the global target to (includes package's components only).