This is an old revision of the document!
Table of Contents
TerraLib and TerraView - Working Environment
Tools
The basic tools you have to install in your environment to work with TerraLib and TerraView are:
| Software | Version | Website |
|---|---|---|
| Git | Latest | http://git-scm.com/ |
| CMake | 2.8.12 | http://www.cmake.org/cmake |
The following tools are optional, and their use is described below:
| Software | Website | Function |
|---|---|---|
| TortoiseGIT | http://code.google.com/p/tortoisegit | General User Interface that makes it easier to use GIT on Windows |
| Git-Cola | http://git-cola.github.io/downloads.html | General User Interface that makes it easier to use GIT on Unix platforms |
| Doxygen | http://sourceforge.net/projects/doxygen/ | used to generate the documentation |
Installing and configuring GIT
Install the latest Git version from: GIT
Follow the default settings, except at:
- Select Components: click Windows Explorer Integration, Git Bash, Git GUI.
- Adjusting you PATH environment: Click third option (Run Git and included Unix Tools …)
- Configuring the line ending conversions: click the first option (Checkout Windows-style, commit Unix-style line endings)
Dependencies
The TerraLib library is split into several modules providing different functionality, therefore, each have a particular set of dependencies. Microsoft Visual Studio 2013/2017 C++ users can download and unpack the suitable third-party libraries compiled for building 64-bit version of TerraLib with Qt5.4.1/Qt5.10 support.
Copy the right one from the links below or access all of them at http://www.dpi.inpe.br/terralib5/terralib5-3rdparty/
| MSVC C++ | QT | TerraView Tags | 3rdparty Zip |
|---|---|---|---|
| 2017 | Qt5.10.1 | 5.4.0 | terralib-5.4.0-3rdparty-msvc-2017-win64 |
| 2013 | Qt5.4.1 | 5.3.x | terralib-5.3.3and5.3.2and5.3.1and5.3.0-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.2.4 | terralib-5.2.4-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.2.3, 5.2.2 | terralib-5.2.2-and-5.2.3-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.2.1 | terralib-5.2.1-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.2.0 | terralib-5.2.0-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.1.0 | terralib-5.1.0-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.0.1 | terralib-5.0.1-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.0.1 | terralib-5.0.1-3rdparty-msvc-2013-win32 |
| 2013 | Qt5.4.1 | 5.0.0 | terralib-5.0.0-3rdparty-msvc-2013-win64 |
| 2013 | Qt5.4.1 | 5.0.0 | terralib-5.0.0-3rdparty-msvc-2013-win32 |
Alternatively, developer working on specific branch improving functionalities, correcting 3rdparty, fixing bugs on “RELEASE-5.Y” branch and so on must take the third party from here:
| Branch | 3rdparty Zip | Comments |
|---|---|---|
| DEVELOP | http://www.dpi.inpe.br/terralib5-devel/3rdparty/bin | Pick the 3rdparty here |
| relelase-5.Y | http://www.dpi.inpe.br/terralib5-devel/3rdparty/bin | Go to the corresponding directory '5.Y' to pick up the right 3rdparty |
The third party dependencies must be uncompressed in a local directory, for example C:\TL5\. After that all dependencies will be at C:\TL5\terralib5-3rdparty-msvc-2017-win64. This location should be part of CMAKE_PREFIX_PATH (CMake tool) when configuring your environment.1)
MacOS and Linux users can check the dependencies document.
Once the environment is ready you can clone terralib source code and build the library. Alternatively, you can download the source code from a zip file .
terraview project, Properties→Configuration Properties→Debugging, set the Environment as PATH=C:\TL5\terralib5-3rdparty-msvc-2017-win64\lib;C:\Qt\Qt5.10.1\5.10.1\msvc2017_64\bin
