docs: add warning about FindPython's Development component when libraries don't…

docs: add warning about FindPython's Development component when libraries don't exist (e.g. on manylinux) (#2689)

* Add waring about FindPython's Development component when libraries don't exist (e.g. on manylinux)

* Minor wording update (thanks, @henryiii!)

docs/compiling.rst

@@ -433,6 +433,14 @@ setting ``Python_ROOT_DIR`` may be the most common one (though with
 virtualenv/venv support, and Conda support, this tends to find the correct
 virtualenv/venv support, and Conda support, this tends to find the correct
 Python version more often than the old system did).
 Python version more often than the old system did).
 
 
+.. warning::
+
+    When the Python libraries (i.e. ``libpythonXX.a`` and ``libpythonXX.so``
+    on Unix) are not available, as is the case on a manylinux image, the
+    ``Development`` component will not be resolved by ``FindPython``. When not
+    using the embedding functionality, CMake 3.18+ allows you to specify
+    ``Development.Module`` instead of ``Development`` to resolve this issue.
+
 .. versionadded:: 2.6
 .. versionadded:: 2.6
 
 
 Advanced: interface library targets
 Advanced: interface library targets