TerraLib and TerraView Wiki Page

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
wiki:terralib50_download [2015/03/31 10:47]
marisa [Source Code From GIT]
wiki:terralib50_download [2015/09/02 18:17] (current)
marisa
Line 1: Line 1:
-====== TerraLib 5.0 and TerraView 5.0 - Download ====== +====== TerraLib 5.0 and TerraView 5.0 - Download ​Source Code ====== 
-   + 
-Before downloading and install TerraLib and TerraView ​source code from GIT repository, make sure you have followed ​the instructions ​to set your [[wiki:​terralib50_environment#​Working Environment]]. Alternatively you can download ​the source ​code from zip file. +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. 
-  + 
-  * Download the available releases of TerraLib and TerraView: +==== Source Code From a .zip file (Windows) ==== 
-    ​* ​[[wiki:​terralib50_download#​From_GIT|Source Code From GIT]] + 
-    ​* ​[[wiki:​terralib50_download#​From_a_zip_file|Source Code From .zip file]]+^Launched^Release^Dependencies^Build Instructions^ 
 +|2015/​09/​02| ​[[@../​download/​download.php?​FileName=terralib-5.0.1.zip|terralib-5.0.1.zip]] |DEPENDENCIES|BUILD_INSTRUCTIONS| 
 +|2015/​06/​10| ​[[@../​download/​download.php?​FileName=terralib-5.0.0.zip|terralib-5.0.0.zip]] |DEPENDENCIES|BUILD_INSTRUCTIONS| 
 + 
 +==== Source Code From .tar.gz ​file (Linux/Mac) ==== 
 + 
 +^Launched^Release^Dependencies^Build Instructions^ 
 +|2015/​09/​02| [[@../​download/​download.php?​FileName=terralib-5.0.1.tar.gz|terralib-5.0.1.tar.gz]] |DEPENDENCIES|BUILD_INSTRUCTIONS| 
 +|2015/​06/​10| [[@../​download/​download.php?​FileName=terralib-5.0.0.tar.gz|terralib-5.0.0.tar.gz]] |DEPENDENCIES|BUILD_INSTRUCTIONS|
  
 +   
 ==== Source Code From GIT ==== ==== Source Code From GIT ====
   ​   ​
 +Before downloading TerraLib and TerraView source code from GIT repository, make sure you have followed the instructions to set your [[wiki:​terralib50_environment#​Working Environment]].
 The GIT repository is located at https://​git.dpi.inpe.br/​terralib5 that must be accessed using: The GIT repository is located at https://​git.dpi.inpe.br/​terralib5 that must be accessed using:
  
-//Username: tester//+  * Username: ​//tester// 
 +  * Password: //​terralibdpi//
  
-//Password: terralibdpi//​ +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.
- +
-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. 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^Release^Git Command^Dependencies^Build Instructions^DoxygenDoc+^Date^Git Command^Dependencies^Build Instructions^ 
-|2015/xx/xx| terralib-5.0.0|%%git clone https://​git.dpi.inpe.br/​terralib5%%|DEPENDENCIES| [[http://​www.dpi.inpe.br/​terralib5/​wiki/​doku.php?​id=wiki:​terralib50_build|General Guide]] or BUILD-INSTRUCTIONS|[[http://​www.dpi.inpe.br/​terralib5/​codedocs_5.0.0/​| Doc5.0.0 ]]|+|2015/06/10|%%git clone https://​git.dpi.inpe.br/​terralib5%%|DEPENDENCIES| [[http://​www.dpi.inpe.br/​terralib5/​wiki/​doku.php?​id=wiki:​terralib50_build|General Guide]] or BUILD-INSTRUCTIONS|
  
-If you experience problems with the SSL certificate try to use the command:+If you experience problems with the SSL certificate try to use the respective ​command ​before git clone:
  
-    ​sudo env GIT_SSL_NO_VERIFY=true git clone https://​tester:​terralibdpi@git.dpi.inpe.br/​terralib5 ​+|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: Go to the directory where the TerraLib and TerraView source code is located:
Line 37: Line 47:
 After cloning, it is possible to checkout a specific tag/branch and create a local branch from this tag/branch to work on. 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.0.0" and create a local branch named "​tag_branch_5.0.0":+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 <​local_branch_tag_name>​ <​one_of_remote_tag_names_listed_by_git_tag_cmd>​
-  git checkout -b tag_branch_5.0. 5.0.0+  git checkout -b tag_branch_5.0. 5.0.1
  
-Alternatively,​ it is possible to checkout one of the branches available. Lets checkout the "​release-5.0.0" branch from where the tag 5.0.originated:+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 <​local_branch_name>​ <​one_of_remote_branches_names_listed_by_git_branch_cmd>​
-  git checkout -b release-5.0.0 ​ release-5.0.0 ​ +  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.x branch into master, thus most of the time there is a release branch related to a tag.+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: There is another branch called "​develop"​ and developers usually should switch to this branch. So, after cloning, switch to the "​develop"​ branch doing:
Line 60: Line 71:
  
  
-=== Source Code From a .zip file === 
-If you are not familiar with GIT, an alternative way is to download the source code of available releases: 
- 
-^Launched^Release^Dependencies^Build Instructions^DoxygenDoc^ 
-|2015/​xx/​xx| [[@../​download/​download.php?​FileName=terralib5.0.0.zip|terralib_5.0.0.zip]] |DEPENDENCIES|BUILD_INSTRUCTIONS|[[http://​www.dpi.inpe.br/​terralib5/​codedocs_5.0.0/​|Doc5.0.0 ]]|