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/06/11 09:44]
castejon [Source Code From a .zip file]
wiki:terralib50_download [2015/09/02 18:17]
marisa
Line 6: Line 6:
  
 ^Launched^Release^Dependencies^Build Instructions^ ^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| |2015/​06/​10| [[@../​download/​download.php?​FileName=terralib-5.0.0.zip|terralib-5.0.0.zip]] |DEPENDENCIES|BUILD_INSTRUCTIONS|
  
Line 11: Line 12:
  
 ^Launched^Release^Dependencies^Build Instructions^ ^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| |2015/​06/​10| [[@../​download/​download.php?​FileName=terralib-5.0.0.tar.gz|terralib-5.0.0.tar.gz]] |DEPENDENCIES|BUILD_INSTRUCTIONS|
  
Line 26: Line 28:
 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^ +^Date^Git Command^Dependencies^Build Instructions^ 
-|2015/06/10|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|+|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 respective command before git clone: If you experience problems with the SSL certificate try to use the respective command before git clone:
Line 45: 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  remote/​origin/​release-5.0.0 or only +  git checkout -b release-5.0 ​ remote/​origin/​release-5.0 or only 
-  git checkout -b release-5.0.0  release-5.0.0  ​(omitting "​remote/​origin"​ part of the branch name)+  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: