Differences

This shows you the differences between two versions of the page.

--- geodma_2:build_inst [2017/06/21 01:44]
raian [Google Mock]
+++ geodma_2:build_inst [2018/10/03 18:49]
raian [External Dependencies]
@@ Line 6: / Line 6: @@
 == Mandatory ==
-   * CMake 3.X (https://cmake.org/)
+   * CMake 3.11.X or Later (https://cmake.org/)
-   * TerraLib 5.X (http://www.dpi.inpe.br/terralib5)
+   * TerraLib 5.4.X (http://www.dpi.inpe.br/terralib5)
-   * Qt 5.X (5.4.2 with opengl recomended - https://download.qt.io/archive/qt/5.4/5.4.2/)
+   * Qt 5.10.X (5.10.1  recomended - https://download.qt.io/official_releases/qt/5.10/5.10.1/)
    * CGAL 4.X (http://www.cgal.org)
-   * Boost 1.58 (In windows, it comes together with TerraLib dependencies)
+   * Boost 1.65 (In windows, it comes together with TerraLib dependencies)
+   * C5.0 Decision Trees Library (https://github.com/rvmaretto/c50_decisionTrees)
    * Python 2.7.X (https://www.python.org) -- **Required** for Code Style checking
@@ Line 21: / Line 22: @@
   * SourceTree Git client for Windows or Mac (recomended)
   * SmartGit Git client for Linux (recomended)
-  * Ms Visual Studio for Windows (2013 recomended)
+  * Ms Visual Studio for Windows (2017 recomended)
   * XCode for Mac OSX (recomended)
@@ Line 30: / Line 31: @@
 Download CMake setup file and install it, adding the cmake command to the PATH environment variable (installer alread has an option to set up this option).
-==== Ms Visual Studio (ref. 2013) ====
+==== Ms Visual Studio (ref. 2017) ====
-In order to build GeoDMA, TerraLib and other dependencies, Ms Visual studio will be needed. We strongly recomend to use the 2013 version, once other versions were not tested.
+In order to build GeoDMA, TerraLib and other dependencies on Windows Environment, Ms Visual studio will be needed. We strongly recomend to use the 2017 version, once other versions were not tested.
 ==== NSIS (ref. 3.01) ====
@@ Line 54: / Line 55: @@
 Download Doxygen from [[http://www.stack.nl/~dimitri/doxygen/download.html]]. Run the installer. We recomend to install it in the default folder //C:/Program Files/doxygen//.
-==== Qt5.X (ref. 5.4.2) ====
+==== Qt5.X (ref. 5.10.1) ====
-Download Qt setup file and install it. After the installation is finished, add the cmake folder from Qt to the PATH environment variable. If you had installed Qt 5.4.2 the default configurations, it will be located at:
+Download Qt setup file and install it. After the installation is finished, add the following folders from Qt to the PATH environment variable. If you had installed Qt 5.10.1 the default configurations, it will be located at:
-   C:\Qt\Qt5.4.2\5.4\msvc2013_64_opengl\lib\cmake
+   C:/Qt/Qt5.10.1/5.10.1/msvc2017_64/lib/cmake/Qt5
+   C:/Qt/Qt5.10.1/5.10.1/msvc2017_64/lib/cmake/Qt5LinguistTools
-==== TerraLib 5.X (ref. release-5.2) ====
+==== TerraLib 5.4.X (ref. release-5.4) ====
 Clone TerraLib from git. In order to do that, you need to first disable the "SSL certificate validation" in your git client. If you are using SourceTree, go to //SourceTree// >> //Preferences// >> //Git// and then check //Disable SSL certificate validation (note: potentially insecure)// to allow downloading TerraLib. Then, clone it from the following Git repository:
@@ Line 65: / Line 68: @@
    https://gitlab.dpi.inpe.br/terralib/terralib.git
-After cloning the repository, set the current branch to the //release-5.2//, which is the currently used by GeoDMA. Further instructions for clonning TerraLib repository, if needed, can be found [[http://www.dpi.inpe.br/terralib5/wiki/doku.php?id=wiki:documentation:devguide:cloning|here]].
+After cloning the repository, set the current branch to the //release-5.4//, which is the currently used by GeoDMA. Further instructions for clonning TerraLib repository, if needed, can be found [[http://www.dpi.inpe.br/terralib5/wiki/doku.php?id=wiki:documentation:devguide:cloning|here]].
-TerraLib has several external dependencies. For windows, a package with all of them is provided, already compiled with //Ms Visual Studio 2013//. This package can be downloaded through the following URL:
+TerraLib has several external dependencies. For windows, a package with all of them is provided, already compiled with //Ms Visual Studio 2017//. This package can be downloaded through the following URL:
-http://www.dpi.inpe.br/terralib5-devel/3rdparty/bin/
+http://www.dpi.inpe.br/terralib5-devel/3rdparty/bin/5.4/
 Instructions to compile these dependencies in MS Windows, if needed, can be found [[http://www.dpi.inpe.br/terralib5/wiki/doku.php?id=wiki:documentation:devguide:dependencies|here]].
@@ Line 81: / Line 84: @@
 Detailed instructions to build TerraLib can be found [[http://www.dpi.inpe.br/terralib5/wiki/doku.php?id=wiki:documentation:devguide:build|here]]
-To build TerraLib, open the CMake GUI, put in //Where is the source code// field the path to the folder //terralib/build/cmake//. Create a directory to build the binaries. We recomend to create the folder //terralib/built//, and put its path in the field //Where to build the binaries//. Then click //Configure//. In the pop up window, select "//Visual Studio 12 2013 Win64//". After the project has finished to configure, click //Generate//. A Visual studio solution called //terralib.sln// will be generated in the binaries folder. Now, just open it and build.
+To build TerraLib, open the CMake GUI, put in //Where is the source code// field the path to the folder //terralib/build/cmake//. Create a directory to build the binaries. We recomend to create the folder //terralib/built//, and put its path in the field //Where to build the binaries//. Then click //Configure//. In the pop up window, select "//Visual Studio 14 2014 Win64//". After the project has finished to configure, click //Generate//. A Visual studio solution called //terralib.sln// will be generated in the binaries folder. Now, just open it and build.
 === Tips and Tricks ===
@@ Line 97: / Line 100: @@
 ==== Google Test ====
 Go to the folder //googletest-1.8.0/googletest/msvc//.
-Inside this folder, there are two Visual Studio solutions. Open the solution called //gtest-md.sln//. This solution was built in an older version of Visual Studio, but Visual Studio automatically convert it to the current version (2013) without problems. After opened, some configurations must be set. This project was built for 32-bit compiling, but we will configure it to generate 64-bit projects. To do this, follow these steps:
+Inside this folder, there are two Visual Studio solutions. Open the solution called //gtest-md.sln//. This solution was built in an older version of Visual Studio, but Visual Studio automatically convert it to the current version (2017) without problems. After opened, some configurations must be set. This project was built for 32-bit compiling, but we will configure it to generate 64-bit projects. To do this, follow these steps:
   - Inside Visual Studio Environment, Right click the solution and go to //Properties//. Then, click "//Configuration Manager...//" button. It will open a pop up window.
@@ Line 113: / Line 116: @@
 Go to the folder //googletest-1.8.0/googlemock/msvc/2010//.
-Inside this folder, open the solution called //gmock.sln//. This solution was built in an older version of Visual Studio (2010), but Visual Studio automatically convert it to the current version (2013) without problems. After opened, some configurations must be set. Like google test, this project was either built for 32-bit compiling, but we will configure it to generate 64-bit projects. To do this, follow these steps:
+Inside this folder, open the solution called //gmock.sln//. This solution was built in an older version of Visual Studio (2010), but Visual Studio automatically convert it to the current version (2017) without problems. After opened, some configurations must be set. Like google test, this project was either built for 32-bit compiling, but we will configure it to generate 64-bit projects. To do this, follow these steps:
   - Inside Visual Studio Environment, Right click the solution and go to //Properties//. Then, click "//Configuration Manager...//" button. It will open a pop up window.
@@ Line 193: / Line 196: @@
    target_link_libraries( CGAL_Qt5 CGAL ${CGAL_3RD_PARTY_LIBRARIES} ${CGAL_Qt5_3RD_PARTY_LIBRARIES} ${Boost_LIBRARIES})
-Create the folder //C:/dev/CGAL-4.10/built//. Then, open CMake Gui. In the field //Where is the source code//, put the folder //C:/dev/CGAL-4.10//. In the field //Where to build the binaries//, put the folder //C:/dev/CGAL-4.10/built// and click //Configure//. In the pop up window, select “Visual Studio 12 2013 Win64” and click //Finish//. After the project has finished to //Configure//, click Generate. A Visual studio solution called //CGAL.sln// will be generated in the binaries folder. Now, just open it and build for Debug and Release configurations.
+Create the folder //C:/dev/CGAL-4.10/built//. Then, open CMake Gui. In the field //Where is the source code//, put the folder //C:/dev/CGAL-4.10//. In the field //Where to build the binaries//, put the folder //C:/dev/CGAL-4.10/built// and click //Configure//. In the pop up window, select “Visual Studio 15 2017 Win64” and click //Finish//. After the project has finished to //Configure//, click Generate. A Visual studio solution called //CGAL.sln// will be generated in the binaries folder. Now, just open it and build for Debug and Release configurations.
 After the solution was built for Debug and Release, you will need to install CGAL in the system. To execute this step, Visual Studio will need administrator privileges. Close Visual Studio. After closed, right click on it and go to //Run as Administrator//. After Visual Studio was opened with administrator privileges, open the solution //CGAL.sln// and build the project //INSTALL// for Debug and Release, respectively.
+==== C5.0 Decision Trees Library ====
 ==== Building GeoDMA ====

Trace:

Differences

Navigation

Search