Doc: indicating how to pass MPI_Comm from mpi4py

[tools/medcoupling.git] / doc / developer / doxygen / doxfiles / reference / cpp / cpp.dox

diff --git a/doc/developer/doxygen/doxfiles/reference/cpp/cpp.dox b/doc/developer/doxygen/doxfiles/reference/cpp/cpp.dox
index 3b2e87c4502fe01f1c7733dbca3c20be259a6045..ef1d78da09c427eb71593df667bfcb3fd5513a77 100644 (file)
--- a/doc/developer/doxygen/doxfiles/reference/cpp/cpp.dox
+++ b/doc/developer/doxygen/doxfiles/reference/cpp/cpp.dox
@@ -21,5 +21,8 @@ data or not.
 For advanced usage, one has to be aware of the stamping mechanism used internally to know
 whether an instance has been modified or not. This is described in the second page above:
  \ref MEDCouplingTimeLabelPage
+
+If your interested into wrapping your C++ code to Python with SWIG and intend to do this in a parallel context
+you might also want to check \ref swig_mpi.
   
   */