X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;ds=sidebyside;f=Doc%2FWebsite%2FDeveloppers.html;h=a76b6d95c049dad37b8ed65ad3e55d24b0f9457c;hb=6dc9a6a8aee263acf3dd2ce1d7f32c51b9133cc0;hp=112cdb75ee2a730c8d6210f716a7927c68ec7de9;hpb=e420fd2a2bf08699d6e01b457f17585ba47a0080;p=gdcm.git
diff --git a/Doc/Website/Developpers.html b/Doc/Website/Developpers.html
index 112cdb75..a76b6d95 100644
--- a/Doc/Website/Developpers.html
+++ b/Doc/Website/Developpers.html
@@ -32,16 +32,17 @@ Please adopt the
All the commits should be atomic. They must preserve the compilation
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.
+ All the commits must correspond to a state of the code where ctest
+ runs and has no failing subtest. Always run ctest before
+ commiting.
Notes:
- - you can start ctest in verbose mode through the command
+
- you can start ctest in verbose mode through the command
ctest -V >& log
- - you can start a single test through ctest with
- ctest -R FailingTestName -V >& log
+
- you can start a single test through ctest with
+ ctest -R FailingTestName -V >& log
@@ -49,13 +50,25 @@ Please adopt the
Compiler flags policy
-When working with gcc please use the following flags when
-configuring the cmake variable CMAKE_CXX_FLAGS
+When working with gcc, please use the following flags when
+configuring the cmake variable CMAKE_CXX_FLAGS
+As a side note 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 flag compiler option.
Sending the result to kitware's dashboard (optional)
@@ -65,9 +78,14 @@ 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.
+the "Experimental Builds" entry.
+UPDATE:Since GDCM moved to its own dashboard there is no possible
+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...
+