X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FDeveloppers.html;h=a8c03af949e807ab38209bd5a11e86f5bbf1238d;hb=8adea4f1eb28ca3e16edc2e9af126ca5bf9b722d;hp=cf6540f4d0e2b724c6e92f6780a410051f4924fb;hpb=c460dc75a10d96fc38011db90fae5bcd8649b743;p=gdcm.git
diff --git a/Doc/Website/Developpers.html b/Doc/Website/Developpers.html
index cf6540f4..a8c03af9 100644
--- a/Doc/Website/Developpers.html
+++ b/Doc/Website/Developpers.html
@@ -11,6 +11,12 @@
Gdcm Developpers
+
+
+DashBoard (look for a "Build Name" containing GDCM)
+
+
+
First you should be familiar on how to
recompile, install and test
gdcm from the
@@ -27,7 +33,7 @@ Please adopt the
in order to prevent checkouts with broken code.
All the commits must correspond to a state of the code where ctest
- runs and has no failing subtest. Always run ctest before commiting.
+ runs and has no failing subtest. Always run ctest before commiting.
Notes:
@@ -43,25 +49,39 @@ Please adopt the
Compiler flags policy
-When working with gcc please use the following flags when
+When working with gcc, please use the following flags when
configuring the cmake variable CMAKE_CXX_FLAGS
+As a side not if you have proper bash/zsh setup cmake automatically
+inspect your CFLAGS and CXXFLAGS. So you can set them up for any
+project. Be carefull though, the quality of your code will greatly
+improve by doing so.
--g -O0 -Wall -W -Wshadow -Wunused-variable -Wunused-parameter
- -Wunused-function -Wunused -Wno-system-headers -Wno-deprecated
- -Woverloaded-virtual
+For CFLAGS:
+ -Wall -W
+
+For CXXFLAGS:
+ -Wall -W -Wshadow -Wunused -Wno-system-headers -Wno-deprecated
+ -Woverloaded-virtual
+For paranoid people, or simply beginner you can also try to compiler gdcm
+using the -pedantic flags compiler option.
Sending the result to kitware's dashboard (optional)
Use ctest -D Experimental.
The results should appear in
-
+
Kitware's dashboard
under the name of your machine (uname). For ease of use you can
-change the SITE variable in your CMakeCache.txt to something more
+change the BUILDNAME variable in your CMakeCache.txt to something more
accurate such as: GDCM-my_machine_name. The entry will then be within
the "Experimental Builds" entry.
+UPDATE:Since GDCM moved to its own dashboard there is no possble
+collision with other project. You can then send dashboard without having
+to properly prepend 'GDCM-' to your cmake BUILDNAME variable. But the
+Win32, mingw, gcc, SunOS is still very important...
+