Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
geodma_2:build_inst [2018/10/03 16:43]
raian [TerraLib 5.4.X (ref. release-5.4)]
geodma_2:build_inst [2018/11/20 10:49] (current)
raian [Building GeoDMA]
Line 6: Line 6:
  
 == Mandatory ==  == Mandatory == 
-   * CMake 3.X (https://​cmake.org/​)+   * CMake 3.11.X or Later (https://​cmake.org/​)
    * TerraLib 5.4.X (http://​www.dpi.inpe.br/​terralib5)    * TerraLib 5.4.X (http://​www.dpi.inpe.br/​terralib5)
    * Qt 5.10.X (5.10.1 ​ recomended - https://​download.qt.io/​official_releases/​qt/​5.10/​5.10.1/​)    * 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)    * 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)    * C5.0 Decision Trees Library (https://​github.com/​rvmaretto/​c50_decisionTrees)
    * Python 2.7.X (https://​www.python.org) -- **Required** for Code Style checking    * Python 2.7.X (https://​www.python.org) -- **Required** for Code Style checking
Line 27: Line 27:
 ===== Windows Environment (ref. 10 x64) ===== ===== Windows Environment (ref. 10 x64) =====
  
-==== CMake 3.X (ref. 3.8.2) ====+==== CMake 3.11.X (ref. 3.12.3) ====
  
 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). 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).
Line 69: Line 69:
  
 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]]. 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/​5.4/​ http://​www.dpi.inpe.br/​terralib5-devel/​3rdparty/​bin/​5.4/​
Line 84: 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]] 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 ​15 2017 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 === === Tips and Tricks ===
Line 100: Line 100:
 ==== Google Test ==== ==== Google Test ====
 Go to the folder //​googletest-1.8.0/​googletest/​msvc//​. 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.   - 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 116: Line 116:
  
 Go to the folder //​googletest-1.8.0/​googlemock/​msvc/​2010//​. 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.   - 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 199: Line 199:
  
 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. 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 ====
 +
 +Clone //C5.0 Decision Trees Library// from the following GitHub repository: ​
 +
 +  https://​github.com/​rvmaretto/​c50_decisionTrees
 +  ​
 +To build the library, open the CMake GUI, put in //Where is the source code// field the path to the folder //​c50_decisionTree/​build/​cmake//​. Create a directory to build the binaries. We recomend to create the folder //​c50_decisionTree/​built//,​ and put its path in the field //Where to build the binaries//.
 +
 +Click //​Configure//​.
 +
 +In the pop up window, select “//Visual Studio 15 2017 Win64//”. After the project has finished to configure, click //​Generate//​. A Visual studio solution called c50_decisionTree.sln will be generated in the binaries folder. Now, just open it and build.
 +
  
 ==== Building GeoDMA ==== ==== Building GeoDMA ====
Line 216: Line 229:
  
 ^ Dependency ​  ​^ ​ Variable ​    ^ Description ​                             ^ Default value             ^ ^ Dependency ​  ​^ ​ Variable ​    ^ Description ​                             ^ Default value             ^
-| TerraLib ​    | terralib_DIR ​ | Folder containing cmake configuration file for TerraLib ​ | C:/Program Files/​terralib5.2.|+| TerraLib ​    | terralib_DIR ​ | Folder containing cmake configuration file for TerraLib ​ | C:/Program Files/​terralib5.4.|
 | TerraLib ​    | terralib_DEPENDENCIES_DIR | Root folder of TerraLib 3rdparty package | ${GEODMA_ROOT_DIR}/​../​dependencies/​terralib5-3rdparty-msvc-2013-win64 | | TerraLib ​    | terralib_DEPENDENCIES_DIR | Root folder of TerraLib 3rdparty package | ${GEODMA_ROOT_DIR}/​../​dependencies/​terralib5-3rdparty-msvc-2013-win64 |
 | TerraLib ​    | terralib_ROOT | Root folder of TeraLib ​               | No default value, automatically searched by CMake | | TerraLib ​    | terralib_ROOT | Root folder of TeraLib ​               | No default value, automatically searched by CMake |
Line 225: Line 238:
 Click //​Configure//​. 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 geodma.sln will be generated in the binaries folder. Now, just open it and build.+In the pop up window, select “//Visual Studio ​15 2017 Win64//”. After the project has finished to configure, click //Generate//. A Visual studio solution called geodma.sln will be generated in the binaries folder. Now, just open it and build.
  
 ===== Linux Environment (ref. ....) ===== ===== Linux Environment (ref. ....) =====

Navigation