Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
geodma_2:build_inst [2018/10/03 16:42] raian [TerraLib 5.X (ref. release-5.2)] |
geodma_2:build_inst [2018/10/03 18:11] raian [Google Mock] |
||
|---|---|---|---|
| Line 68: | Line 68: | ||
| https://gitlab.dpi.inpe.br/terralib/terralib.git | 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 2013//. This package can be downloaded through the following URL: | ||
| 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 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 === | === 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. | ||
