X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FDeveloppers.html;h=191421e6e5a929975aa77eafef15a530d8c3cf70;hb=9f5d2df7b2426f31f4f802542986ec0233046b28;hp=a8c03af949e807ab38209bd5a11e86f5bbf1238d;hpb=7ab6ec3467d07f22144e60f63f357ffd9cf2e484;p=gdcm.git
diff --git a/Doc/Website/Developpers.html b/Doc/Website/Developpers.html
index a8c03af9..191421e6 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,22 +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
-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
+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.
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.
+using the -pedantic flag compiler option.
Sending the result to kitware's dashboard (optional)
@@ -74,12 +78,12 @@ The results should appear in
Kitware's dashboard
under the name of your machine (uname). For ease of use you can
-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
+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 possible
collision with other project. You can then send dashboard without having
-to properly prepend 'GDCM-' to your cmake BUILDNAME variable. But the
+to properly prepend 'GDCM-' to your cmake BUILDNAME variable. But the
Win32, mingw, gcc, SunOS is still very important...