TerraLib and TerraView Wiki Page

You are here: start » wiki » terralib5_build

Differences

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

--- wiki:terralib5_build [2014/08/13 16:25]
marisa
+++ wiki:terralib5_build [2014/09/25 15:55]
marisa
@@ Line 1: / Line 1: @@
-====== TerraLib 5.0.0-alpha - Build and Install ======
+====== TerraLib 5.0 - General guide for Building and Install ======
 Useful links:
-  * [[wiki:terralib5_build#general_information| General Informationm]]
+  * [[wiki:terralib5_build#CMake_Command_Line_Notes| Using Cmake Command line]]
-  * [[wiki:terralib5_build#Cmake-GUI| Using the Cmake-GUI]]
-  * [[wiki:terralib5_build#Cmake_Command_Line| Using Cmake Command line]]
-  * [[wiki:terralib5_build#ccmake| Using Ccmake]]
-  * [[wiki:terralib5_build#building_the_examples| Examples]]
 ===== Building Terralib =====
-This section explains how to build the TerraLib from source code in some platforms. The original instructions are in BUILD-INSTRUCTIONS file at the terralib codebase.
+This section explains how to build the TerraLib from source code in some platforms. The most updated instructions are in BUILD-INSTRUCTIONS file located at the root of the terralib codebase directory. Here are the general instructions and might not have all variables needed for a specific release.
+==== 1. Build instructions on Linux with g++ (GNU gcc) ====
+-----------------------------------------------------------
+.1. Open a Command Prompt (Shell).
+.2. We will assume that the codebase (all the source tree) is located at:
+/home/user/terralib/codebase
+.3. Create a folder out of the terralib source tree, for example:
+  $ cd /home/user/terralib
+  $ mkdir build-linux
+  $ cd build-linux
+.4. For Linux systems you must choose the build configuration:
+  $ cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE:STRING="Release" -DCMAKE_INSTALL_PREFIX:PATH="/usr/local/terralib" ../codebase/build/cmake
+Notes:
+  a) Some Linux flavours with different versions of GNU gcc and Boost will need more parameters such as:
+          -DCMAKE_PREFIX_PATH:PATH="/usr/local;/opt/include"
+          -DCMAKE_INCLUDE_PATH:PATH="/usr/local;/opt/include"
+          -DCMAKE_LIBRARY_PATH:PATH="/usr/local;/opt/lib"
+          -DCMAKE_PROGRAM_PATH:PATH="/usr/local/bin;/opt/bin"
+          -DBOOST_ROOT:PATH="/opt/boost"
+  b) Boost can also be indicated by BOOST_INCLUDEDIR (note: without an '_' separating INCLUDE and DIR):
+          -DBOOST_INCLUDEDIR:PATH="/usr/local/include"
+  c) The parameter -lpthread must be informed only if your Boost was not built as a shared library:
+          -DCMAKE_CXX_FLAGS:STRING="-lpthread"
+  d) For building with Qt5 you can provide the Qt5_DIR variable as:
+          -DQt5_DIR:PATH="/usr/local/lib/cmake/Qt5"
+  e) For generating a debug version set CMAKE_BUILD_TYPE as:
+          -DCMAKE_BUILD_TYPE:STRING="Debug"
+.5 Building:
+  $ make -j 4
+.6 Installing:
+  $ make install
+==== 2. Building with CMake GUI ====
+--------------------------
+.1 On Windows:
 a) We will assume that the TerraLib source tree (git clone) is located at:
@@ Line 65: / Line 116: @@
 For more information on TerraLib, please, visit its main web page at: http://www.terralib.org.
-==== Cmake-Gui  ====
-Using the Graphic Interface (cmake-gui) to build the compilation projects.
+==== CMake command line notes====
-To run CMake from the cmake-gui, you will:
-  * Execute the cmake-gui system, found in the CMake binary folder.
-  * In the "Where is the source code", put the path where is the CMakeLists main file. For terralib it is <terralib_root>/build
-  * In the "Where to build the binaries", put the path where you want the CMake generate the files. For terralib it can be <building_dir>/terralib.
-  * (Optional) Set up the TE_DEPENDENCIES_DIR. Press the Add Entry button and adjust the path to the dependencies directory, for example:
-{{ :wiki:add-entry.png?400 |}}
-  *  Click "Configure" and select the generator for the project.
-  * Review the "BUILD" group and check which module you want to build.
-  * Review the options related to third-party libraries (e.g. "Boost" or "Gdal") and make sure that CMake found the needed library file(s) and include directoriy. If any of the dependencies is not found you must manually enter the path to it. Just click on the line of the dependency and type the path.
-  * Click "Generate"
-After these steps, the build files will have been generated and the cmake-gui will look like this:
-{{ :wiki:cmake-gui.png?1080 |}}
-Now all you need to do is go to the selected building directory and run the appropriate building tool according to the generator you selected. (e.g. for Unix Makefiles just run "make").
-==== CMake command line ====
 Using the CMake command line to build the compilation projects.
@@ Line 107: / Line 129: @@
 ^Variable^Effect^Example^
 | CMAKE_BUILD_TYPE | Sets the build type. Such as Debug or Release | -DCMAKE_BUILD_TYPE=Debug |
-| BUILD_TERRALIB4 | Enable/disable [ON/OFF] the TerraLib4 module | -DBUILD_TERRALIB4=OFF |
 | QWT_INCLUDE_DIR | Sets the include path of the QWT library | -DQWT_INCLUDE_DIR=<DIRECTORY> |
 | QWT_LIBRARY_DEBUG | Sets the path of the QWT library in Debug | -DQWT_LIBRARY_DEBUG=<LIBRARY_FILE_PATH> |
 | QWT_LIBRARY_RELEASE | Sets the path of the QWT library in Release | -DQWT_LIBRARY_RELEASE=<LIBRARY_FILE_PATH> |
-| TE_DEPENDENCIES_DIR | Used as an easy and convenient way to locate terralib's dependencies | -DTE_DEPENDENCIES_DIR=<unpack_dir>/terralib_3rdparty_win32 |
 | LOG4CXX_INCLUDE_DIR | Log4Cxx headers include path | -DLOG4CXX_INCLUDE_DIR=<DIRECTORY> |
 | LOG4CXX_LIBRARY_DEBUG | Log4Cxx debug library file path | -DLOG4CXX_LIBRARY_DEBUG=<LIBRARY_FILE_PATH> |
@@ Line 138: / Line 158: @@
 A few examples of how to call CMake to build terralib:
+  * Calling from a building dir while pointing to the source (main CmakeLists location), specifying Unix Makefiles as a generator, compiling in Release
+  $ cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH="/usr/local/terralib" ../codebase/build/
   * Specifying Visual Studio 10 as the generator, using source code located at C:\Dev\Terralib\build and setting the option to generate a NSIS installer as true:
-cmake -G 'Visual Studio 10' C:\Dev\Terralib\build -DTE_DEPENDENCIES_DIR=C:/Libs/terralib_3rdparty_win32 -DCPACK_BINARY_NSIS=True
+  $ cmake -G 'Visual Studio 10' C:\Dev\Terralib\build -DTE_DEPENDENCIES_DIR=C:/Libs/terralib_3rdparty_win32 -DCPACK_BINARY_NSIS=True
   * Calling from a building dir while pointing to the source (main CmakeLists location), specifying Unix Makefiles as a generator, compiling in Release and adjusting the QWT references to the path of a locally compiled version:
-cmake -G 'Unix Makefiles' /home/<user>/terralib5/build -DCMAKE_BUILD_TYPE=Release -DQWT_INCLUDE_DIR=/usr/local/qwt-6.1.0/ include -DQWT_LIBRARY_RELEASE=/usr/local/qwt-6.1.0/lib/libqwt.so.6.1.0
+  $ cmake -G 'Unix Makefiles' /home/<user>/terralib5/build -DCMAKE_BUILD_TYPE=Release -DQWT_INCLUDE_DIR=/usr/local/qwt-6.1.0/include -DQWT_LIBRARY_RELEASE=/usr/local/qwt-6.1.0/lib/libqwt.so.6.1.0
 == Notes for Linux build ==
@@ Line 154: / Line 178: @@
 | LD_LIBRARY_PATH | A colon-separated set of directories where third party libraries should be searched for first, before the standard set of directories | LD_LIBRARY_PATH=/home/user/mylibraries |
-==== CCmake ====
-Using the curses based Interface (ccmake) to build the compilation projects.
-On some Unix platforms, you can install a curses based cmake gui that is a terminal based text application and can be used as well. The commands are basically the same as before, but instead of using "cmake" use "ccmake" instead.
-Example: ccmake /home/<username>/source/terralib5/build (Executed from the <building_dir>)
-{{ :wiki:ccmake.png?1080 |}}
-Once executed, the user can manually adjust the variables and customize the compilation. Once the options have been adjusted type c to configure the project and then type g to generate the build files and exit ccmake.
-===== Building the Examples =====
-This section will detail the proccess of building the examples after building or installing Terralib. Some examples are listed here:
-^  Folder  ^  Content   ^
-| example_ado| It shows how to interact with Microsoft Access driver. |
-| example_dataaccess| It shows how to interact with DataAccess Module and drivers PostGIS, ORG and GDAL|
-| example_geometry| It shows how to create geometries and some Spatial Operators.|
-| terralib_raster| It shows how to manipulate raster data.|
-| example_rp| It show how use the raster processing module.|
-| example_srs| It shows how to use the sapatial reference system manager. |
-| example_st| It show how to use the Spatial Temporal Module.|
-| example_vp| It shows how to use the Vector Processing Module.|
-The proccess is similar to Terralib's proccess, steps such as using the cmake-gui or command line are similar, however, there a few differences worth mentioning.
-First, in order to build either the examples cmake must be told where is the CMakeLists main file which is <terralib_root>/build/examples.
-Also, examples use a few variables that can edited, they are:
-^Variable^Comment^Value^
-|terralib_DIR | Where terralib has been built/installed | it can either  be defined as an environmental variable or be defined at the CMake interface using the Add Entry button, type PATH, value <building_dir>/terralib |
-| DATA_DIR  | where the data used by the examples will be downloaded and unpacked  | Inform the path where you downloaded the http://www.dpi.inpe.br/terralib5/data.zip |
-After pressing ''Configure'', Review the "EXAMPLE" group and check which example you want to build. Some are already checked and you can keep or change the examples that will be compiled, for example:
-{{:wiki:examples-compilation.png|}}
-You can edit these variables in the same way used to configure terralib's variables.
-Once you are done, just ''Configure'' and ''Generate'' the build files in the same way explained on the terralib section.

Trace:

TerraLib and TerraView Wiki Page

Differences

Navigation

Search