The source code of terralib and terraview (as one of its modules) can be downloaded directly from a zip file or from a GIT repository. Once you have the code follow the instructions on the files BUILD-INSTRUCTIONS and DEPENDENCIES located at the root of terralib source tree.
Launched | Release | Dependencies | Build Instructions |
---|---|---|---|
2015/09/02 | terralib-5.0.1.zip | DEPENDENCIES | BUILD_INSTRUCTIONS |
2015/06/10 | terralib-5.0.0.zip | DEPENDENCIES | BUILD_INSTRUCTIONS |
Launched | Release | Dependencies | Build Instructions |
---|---|---|---|
2015/09/02 | terralib-5.0.1.tar.gz | DEPENDENCIES | BUILD_INSTRUCTIONS |
2015/06/10 | terralib-5.0.0.tar.gz | DEPENDENCIES | BUILD_INSTRUCTIONS |
Before downloading TerraLib and TerraView source code from GIT repository, make sure you have followed the instructions to set your Working Environment. The GIT repository is located at https://git.dpi.inpe.br/terralib5 that must be accessed using:
To get the TerraLib and TerraView source code under your current directory, use the git clone
command bellow in a Prompt Dos or Git Bash window.
After cloning, a terralib5 directory is created and the DEPENDENCIES and BUILD-INSTRUCTIONS files can be accessed. Make sure all dependencies are installed before building.
Date | Git Command | Dependencies | Build Instructions |
---|---|---|---|
2015/06/10 | git clone https://git.dpi.inpe.br/terralib5 | DEPENDENCIES | General Guide or BUILD-INSTRUCTIONS |
If you experience problems with the SSL certificate try to use the respective command before git clone:
Windows | git config --global http.sslVerify false |
Linux/MAC | sudo env GIT_SSL_NO_VERIFY=true git clone https://tester:terralibdpi@git.dpi.inpe.br/terralib5 |
Go to the directory where the TerraLib and TerraView source code is located:
cd terralib5
Useful git commands can be used to list all branch or tag:
git branch -a //it lists all branches and the current one prefixed with star "*master" git tag -l //it lists all tags
After cloning, it is possible to checkout a specific tag/branch and create a local branch from this tag/branch to work on.
Lets checkout the latest release tagged with number “5.x.x” and create a local branch named “tag_branch_5.x.x”:
git checkout -b <local_branch_tag_name> <one_of_remote_tag_names_listed_by_git_tag_cmd> git checkout -b tag_branch_5.0.1 5.0.1
Alternatively, it is possible to checkout one of the branches available. Lets checkout the “release-5.0” branch from where the tag 5.0.x (x varying from 1 to n) originated:
git checkout -b <local_branch_name> <one_of_remote_branches_names_listed_by_git_branch_cmd> git checkout -b release-5.0 remote/origin/release-5.0 or only git checkout -b release-5.0 release-5.0(omitting "remote/origin" part of the branch name)
It is worth mention that a tag is created only into the master branch after merging a release-x.x branch into master, thus most of the time there is a release branch related to a tag.
There is another branch called “develop” and developers usually should switch to this branch. So, after cloning, switch to the “develop” branch doing:
git branch -a // current branch after clone is *master git checkout -b develop develop
If you are not familiar with GIT commands, you can use a graphical GIT client like TortoiseGIT (for Windows) or Git-Cola (for Linux, Mac and Windows).
Now it is time to build the working environment. Use the BUILD-INSTRUCTIONS file located at the root of terralib5 source tree. Alternatively, use the General Guide instructions.