From a1101a8d847ca0c1200e3f3bedeb518216058fb5 Mon Sep 17 00:00:00 2001 From: Kerautret Date: Tue, 24 Jan 2017 14:20:45 +0100 Subject: [PATCH] doc fix from issue #1218 --- src/DGtal/doc/moduleBuildDGtal.dox | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/src/DGtal/doc/moduleBuildDGtal.dox b/src/DGtal/doc/moduleBuildDGtal.dox index 7571d9a311..0d56c91c40 100644 --- a/src/DGtal/doc/moduleBuildDGtal.dox +++ b/src/DGtal/doc/moduleBuildDGtal.dox @@ -67,8 +67,12 @@ package name and versions. An important feature of cmake is the "out-of-source" build process. Let us suppose that DGtal sources are in the DGTALSOURCES -folder. Hence, in a terminal you can create a build folder: @code cd -DGTALSOURCES mkdir build cd build @endcode +folder. Hence, in a terminal you can create a build folder: +@code +cd DGTALSOURCES +mkdir build +cd build +@endcode Next, use the cmake command to generate your Unix Makefile project (default generator on Unix/Linux) like below for the minimal DGtal configuration: @@ -146,7 +150,7 @@ tools with recent Visual Studio target. During the project generation, you would have to specify the path to @e boost headers (or paths needed for any optional dependency such as GMP, CGAL, Cairo...). -@note Do not forget to set @e BUILD_SHARED_LIBS cmake to falqse (static DGtal lib target). +@note Do not forget to set @e BUILD_SHARED_LIBS cmake to false (static DGtal lib target). @advanced When working on DGtal within github, we have set up a Windows