HPX GIT Repository

HPX-5 Home / Applications / Documentation / Frequently Asked Questions /
GIT Repository /Media / Presentations / Publications /
Users Guide / Vision / CREST Home
This page is for developers who want to work on the internals of HPX-5 itself. If you are looking to simply download and install HPX-5, please click here.

Browse the HPX-5 Git Repository

The central HPX-5 GitLab repo holds two main branches with an infinite lifetime: master and develop. The Git master branch is the stable release version of HPX-5. We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state. We consider origin/develop to be the main branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release. This is where any nightly regression CI builds are built from. The head of the development code tree, develop branch is not guaranteed to be stable. For the most part, we try very hard to not commit things that are broken, but this is an active development branch bugs can happen. If you find any bugs, please report them!

Cloning the Repository

Clone the main HPX-5 Git repo at Gitlab. The main development work occurs on the develop branch in this repo.

shell$ git clone https://gitlab.crest.iu.edu/extreme/hpx.git
Cloning into ‘hpx’…
remote: Counting objects: 69554, done.
remote: Compressing objects: 100% (21237/21237), done.
remote: Total 69554 (delta 50997), reused 65170 (delta 47501)
Receiving objects: 100% (69554/69554), 26.99 MiB | 18.59 MiB/s, done.
Resolving deltas: 100% (50997/50997), done.
Checking connectivity… done.






Once you have successfully cloned the repository, continue on to the instructions on how to build from a developer checkout.

Note that Git is natively capable of using many forms of web proxies. If your network setup requires the user of a web proxy, consult the Git documentation for more details.

Commit access to HPX-5’s git repository:

Commit access is granted to contributors with a track record of submitting high quality patches. Your changes are subject to code review (either before or after they are committed, depending on the nature of the change). If you would like committing access, please send an email to Systems Administrator at “sysadmin[at]crest[dot]iu[dot]edu” with the following information:

  • The user name you want to commit with.
  • Your full name, email address and organizational affiliation.