|
3 | 3 | Installation/Updates |
4 | 4 | #################### |
5 | 5 |
|
6 | | -Clone OSVVM Libraries |
7 | | -********************* |
| 6 | +.. image:: https://img.shields.io/badge/OSVVM-OsvvmLibraries-EDB74E.svg?longCache=true&logo=GitHub&labelColor=333333 |
| 7 | + :alt: Sourcecode on GitHub |
| 8 | + :height: 22 |
| 9 | + :target: https://github.com/OSVVM/OsvvmLibraries |
| 10 | +.. image:: https://img.shields.io/github/v/tag/OSVVM/OsvvmLibraries |
| 11 | + :target: https://github.com/OSVVM/OsvvmLibraries/releases/latest |
| 12 | + :alt: GitHub Release |
| 13 | + |
| 14 | +OSVVM is hosted and developed on https://github.com/OSVVM. It's components are split into multiple Git repositories, |
| 15 | +which be used individually or as a group. The all-in-one repository is called |
| 16 | +`OsvvmLibraries <https://github.com/OSVVM/OsvvmLibraries>`__. |
8 | 17 |
|
9 | | -Download OSVVM Libraries |
10 | | -************************ |
11 | 18 |
|
12 | 19 | OSVVM is available as either a git repository OSVVM Libraries or a zip file from osvvm.org Downloads Page. |
13 | 20 |
|
14 | | -On GitHub, all OSVVM libraries are a submodule of the repository OsvvmLibraries. Download all OSVVM libraries using |
15 | | -``git clone`` with the ``–recursive`` flag: |
| 21 | +Clone OsvvmLibraries |
| 22 | +******************** |
| 23 | + |
| 24 | +OsvvmLibraries summarizes all OSVVM repositories into a single parent repository, which has OSVVM's components |
| 25 | +registered as Git submodules. |br| |
| 26 | +When cloning ensure to append the ``–recursive`` flag. |
| 27 | + |
| 28 | +.. code-block:: bash |
| 29 | +
|
| 30 | + git clone --recursive https://github.com/OSVVM/OsvvmLibraries.git |
| 31 | +
|
| 32 | +.. seealso:: |
| 33 | + |
| 34 | + Git Documentation: `git clone <https://git-scm.com/docs/git-clone>`__ |
| 35 | + |
| 36 | + |
| 37 | +Register OsvvmLibraries as Git Submodule |
| 38 | +**************************************** |
| 39 | + |
| 40 | +Usually, OSVVM will be part of a bigger HDL project structure also maintained in Git. Therefore, it's best to integrate |
| 41 | +OSVVM as a submodule into that project. The following commands assume, OSVVM gets added into ``./lib/OsvvmLibraries``. |
16 | 42 |
|
17 | 43 | .. code-block:: bash |
18 | 44 |
|
19 | | - git clone --recursive https://github.com/osvvm/OsvvmLibraries |
| 45 | + cd <project>/lib |
| 46 | + git submodule add https://github.com/OSVVM/OsvvmLibraries.git |
| 47 | + git submodule update --init --recursive |
| 48 | +
|
| 49 | +.. seealso:: |
| 50 | + |
| 51 | + Git Documentation: `git submodule add <https://git-scm.com/docs/git-submodule>`__ |
| 52 | + |
| 53 | + |
| 54 | +Register Individual VCs as Git Submodule |
| 55 | +**************************************** |
| 56 | + |
| 57 | +.. todo:: |
| 58 | + |
| 59 | + describe individual submodule workflow |
| 60 | + |
| 61 | +Updating OSVVM or OSVVM Components |
| 62 | +********************************** |
| 63 | + |
| 64 | +.. todo:: |
| 65 | + |
| 66 | + describe update process using Git |
| 67 | + |
| 68 | + |
| 69 | +Download OSVVM Libraries |
| 70 | +************************ |
| 71 | + |
| 72 | +.. image:: https://img.shields.io/github/v/release/OSVVM/OsvvmLibraries |
| 73 | + :target: https://github.com/OSVVM/OsvvmLibraries/releases/latest |
| 74 | + :alt: GitHub Release |
| 75 | + |
| 76 | +OsvvmLibraries is also offered as an archive at https://github.com/OSVVM/OsvvmLibraries/releases/latest |
| 77 | + |
| 78 | +* ``https://github.com/OSVVM/OsvvmLibraries/releases/download/<version>/OsvvmLibraries-<version>.tar.gz`` |
| 79 | +* ``https://github.com/OSVVM/OsvvmLibraries/releases/download/<version>/OsvvmLibraries-<version>.tar.zstd`` |
| 80 | +* ``https://github.com/OSVVM/OsvvmLibraries/releases/download/<version>/OsvvmLibraries-<version>.zip`` |
| 81 | + |
| 82 | +.. attention:: |
| 83 | + |
| 84 | + Downloading the archive provided by GitHub's source code download doesn't include the submodule's code. Therefore |
| 85 | + OSVVM added a CI job for packaging all sources (incl. submodules) into a single archive. |
| 86 | + |
| 87 | + |
| 88 | +Business Continuity Planning |
| 89 | +**************************** |
| 90 | + |
| 91 | +.. todo: |
| 92 | +
|
| 93 | + describe fork structure |
| 94 | +
|
| 95 | + 1. fork on GitHub |
| 96 | + 2. mirror to local Git server (e.g. GitLab) |
| 97 | + 3. clone to local machine |
| 98 | +
|
0 commit comments