diff --git a/Docs/source/developers/local_compile.rst b/Docs/source/developers/local_compile.rst
index e534a1662c1..8bfa033a92d 100644
--- a/Docs/source/developers/local_compile.rst
+++ b/Docs/source/developers/local_compile.rst
@@ -57,6 +57,7 @@ When building WarpX, :ref:`the following CMake flags <building-cmake-options>` w
      -DWarpX_pybind11_src=$HOME/src/pybind11
 
    cmake --build build -j 8
+   cmake --build build -j 8 --target pip_install
 
 
 .. _developers-local-compile-findpackage:
@@ -86,6 +87,7 @@ WarpX supports this with :ref:`the following CMake flags <building-cmake-options
      -DWarpX_pybind11_internal=OFF
 
    cmake --build build -j 8
+   cmake --build build -j 8 --target pip_install
 
 As a background, this is also the workflow how WarpX is built in :ref:`package managers such as Spack and Conda-Forge <install-dependencies>`.
 
diff --git a/Docs/source/install/cmake.rst b/Docs/source/install/cmake.rst
index 1f52b4f290f..d1dc25cf095 100644
--- a/Docs/source/install/cmake.rst
+++ b/Docs/source/install/cmake.rst
@@ -329,6 +329,7 @@ This is the workflow most developers will prefer as it allows rapid re-compiles:
    # build & install Python only
    cmake --build build -j 4 --target pip_install
 
+There is also a ``--target pip_install_nodeps`` option that :ref:`skips pip-based dependency checks <developers-local-compile-pylto>`.
 
 WarpX release managers might also want to generate a self-contained source package that can be distributed to exotic architectures: