From 9231ddefc8add6519a7ca5fc47a5cb7c7e6d9f1f Mon Sep 17 00:00:00 2001
From: Virgile Prevosto <virgile.prevosto@m4x.org>
Date: Fri, 3 Dec 2021 17:53:01 +0100
Subject: [PATCH] [devman] Mention lablgtk3 issue with Dgraph in the tutorial

---
 doc/developer/tutorial.tex | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/doc/developer/tutorial.tex b/doc/developer/tutorial.tex
index 4d1f208a3d1..737008eb49d 100644
--- a/doc/developer/tutorial.tex
+++ b/doc/developer/tutorial.tex
@@ -976,6 +976,15 @@ CFG'' item appears, that displays the control flow graph of the
 function in a dialog box. This is achieved just by appending the following
 pieces of code at the end of the \texttt{cfg\_print.ml} file.
 
+\begin{important}
+Frama-C GUI can be compiled against two versions of lablgtk (the OCaml
+bindings to the Gtk toolkit). The actual rendering of the control flow graph
+is actually done by the external OCamlgraph library, and only available
+when compiling against lablgtk2. If you're using lablgtk3,
+you will only see a pop-up window indicating that there's no support for
+displaying graphs.
+\end{important}
+
 Currently, we used a visitor that outputs a \dottool file with the CFG of
 all functions of all files. We use \texttt{dump\_function} to output
 the CFG of a single function instead.
@@ -993,7 +1002,7 @@ Now we write the GUI extension code:
 \scodeidx{Pretty\_source}{PVDecl}
 \sscodeidx{Globals}{Functions}{get}
 \scodeidx{Kernel\_function}{get\_definition}
-\scodeidx{Gtk\_helper}{graph\_window}
+\scodeidx{Dgraph\_helper}{graph\_window}
 \scodeidx{Design}{register\_extension}
 \sscodeidx{Design}{main\_window\_extension\_points}{register\_source\_selector}
 
-- 
GitLab