Merge pull request #711 from fspindle/feat_release_3_3_0

Feat release 3 3 0

ChangeLog

@@ -6,7 +6,7 @@
                       https://visp.inria.fr
 
 
-ViSP 3.2.1 (under work)
+ViSP 3.3.0 (released February 14, 2020)
   - Contributors:
     . This release was possible thanks to contributions from Fabien Spindler,
       Souriya Trinh, Gatien Gaumerais, Yasutomo Shirahama, Yash Kapoor, Noura Neji,
@@ -35,7 +35,7 @@ ViSP 3.2.1 (under work)
       vpRealSense2 class
     . Compatibility with Windows 10 SDK latest version to enable vpDisplayGDI
       usage
-    . Compatibility with Fedora 30
+    . Compatibility with Fedora 31
     . Compatibility with Raspberry 4 Alpine
     . New option to select CXX standard set by default to c++11
     . Introduce a timeout (default to 50ms) during DataMatrix code detection
@@ -94,6 +94,7 @@ ViSP 3.2.1 (under work)
     . [#669] Fix segfault and memory leak when BEST_RESIDUAL_VIRTUAL_VS or
       HOMOGRAPHY_ORTHOGONAL_ITERATION pose estimation method are used
     . [#679] Fix display
+    . [#706] visp.pc pkg-config file not conform to man page
 ----------------------------------------------
 ViSP 3.2.0 (released January 23, 2019)
   - Contributors:

doc/mainpage.doc.in

@@ -116,7 +116,6 @@ href="https://visp.inria.fr/publications" target="_parent">https://visp.inria.fr
 - \ref tutorial-getting-started <br>This tutorial shows how to build a project that uses ViSP to read and display an image.
 - \ref tutorial-getting-started-naoqi <br>This tutorial shows how to build a project that uses ViSP on NAOqi OS running on NAO, Romeo or Pepper humanoid robots.
 - \ref tutorial-import-visp-into-EclipseIDE <br>This tutorial shows how to import a CMake project that uses ViSP in Eclipse IDE.
-- \ref tutorial-contrib-module <br>This tutorial explains how to exploit ViSP modular architecture in order to introduce a new contrib module.
 
 \subsection tuto_image Image manipulation
 
@@ -210,6 +209,11 @@ in one thread and display these images in an other thread.
 
 - \ref tutorial-add-new-dependency <br>This tutorial explains how to introduce a new class that relies on a 3rd party SDK. Different use cases are given as example.
 
+\subsection tuto_contrib Extanding ViSP with contrib modules
+
+- \ref tutorial-contrib-module <br>This tutorial explains how to exploit ViSP modular architecture in order to introduce a new contrib module.
+
+
 \section Citing_ViSP Citing ViSP
 
 Please cite ViSP in your publications if it helps your research:

doc/tutorial/tutorial.doc

@@ -42,6 +42,8 @@ This page references all the tutorials in developer zone.
 
 - \subpage tutorial_coding
 
+- \subpage tutorial_contrib
+
 */
 
 /*! \page tutorial_ios ViSP for iOS
@@ -131,7 +133,6 @@ This page introduces the user to the way to start with ViSP.
 - \subpage tutorial-getting-started <br>This tutorial shows how to build a project that uses ViSP to read and display an image.
 - \subpage tutorial-getting-started-naoqi <br>This tutorial shows how to build a project that uses ViSP on NAOqi OS running on NAO, Romeo or Pepper humanoid robots.
 - \subpage tutorial-import-visp-into-EclipseIDE <br>This tutorial explains how to import a CMake project in Eclipse IDE.
-- \subpage tutorial-contrib-module <br>This tutorial explains how to exploit ViSP modular architecture in order to introduce a new contrib module.
 
 */
 
@@ -248,3 +249,10 @@ This page introduces the way ViSP source code can be modified with new contribut
 - \subpage tutorial-add-new-dependency <br>This tutorial explains how to introduce a new class that relies on a 3rd party SDK. Different use cases are given as example.
 
 */
+
+/*! \page tutorial_contrib Extanding ViSP with contrib modules  
+This page introduces the way ViSP source code can be modified with new contributions.
+
+- \subpage tutorial-contrib-module <br>This tutorial explains how to exploit ViSP modular architecture in order to introduce a new contrib module.
+
+*/

platforms/scripts/valgrind/valgrind_visp.supp

@@ -668,3 +668,21 @@
    fun:_ZNSt3__113basic_ostreamIcNS_11char_traitsIcEEE3putEc
 }
 
+#==18150== 231 bytes in 1 blocks are still reachable in loss record 101 of 169
+#==18150==    at 0x5FD1: malloc (in /usr/local/Cellar/valgrind/3.15.0/lib/valgrind/vgpreload_memcheck-amd64-darwin.so)
+#==18150==    by 0xD3BBD5: currentlocale (in /usr/lib/system/libsystem_c.dylib)
+#==18150==    by 0xA4833: vpMbtXmlGenericParser::vpMbtXmlGenericParser(int) (vpMbtXmlGenericParser.cpp:1455)
+#==18150==    by 0x9C895: vpMbTracker::loadConfigFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) (vpMbTracker.cpp:3788)
+#==18150==    by 0x69988: vpMbGenericTracker::TrackerWrapper::loadConfigFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) (vpMbGenericTracker.cpp:6216)
+#==18150==    by 0x5C454: vpMbGenericTracker::loadConfigFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) (vpMbGenericTracker.cpp:2809)
+#==18150==    by 0x100009F86: bool (anonymous namespace)::run<unsigned char>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool, bool, bool, int, int, bool, bool, bool) (testGenericTracker.cpp:285)
+#==18150==    by 0x1000056B5: main (testGenericTracker.cpp:701)
+{
+   visp-osx-std::locale
+   Memcheck:Leak
+   match-leak-kinds: reachable
+   fun:malloc
+   ...
+   fun:currentlocale
+   fun:_ZN21vpMbtXmlGenericParserC2Ei
+}