Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:user_software:user_software [2011-10-14 12:55] – Lars Bahren | public:user_software:user_software [2017-03-08 15:27] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== User Software ====== | + | ~~NOTOC~~ |
+ | |||
+ | ====== | ||
+ | |||
+ | < | ||
+ | <div style=" | ||
+ | </ | ||
+ | |||
+ | __TOC__: | ||
+ | |||
+ | - [[#Code repository]] | ||
+ | * [[# | ||
+ | * [[#Checking out code]] / Read access | ||
+ | * [[#Updating your working copy]] | ||
+ | * [[#Write access to the repository]] | ||
+ | - **Software packages** | ||
+ | * [[CR-Tools]] | ||
+ | * [[DAL|Data Access Library]] (DAL) | ||
+ | * [[http:// | ||
+ | * [[LOPES-Eventbrowser]] | ||
+ | * < | ||
+ | * [[http:// | ||
+ | * [[Pulsar Tools]] | ||
+ | * < | ||
+ | - [[Building an individual package]] | ||
+ | - [[# | ||
+ | - [[Reorganization of the software collection]] | ||
==== Code repository ==== | ==== Code repository ==== | ||
- | === Internal structure | + | === Organization of the repository |
< | < | ||
- | lus.lofar.org/ | + | usg.lofar.org/ |
|-- code | |-- code | ||
| |-- branches | | |-- branches | ||
| `-- trunk | | `-- trunk | ||
- | | | + | | |
| | | | ||
| | | | ||
Line 21: | Line 47: | ||
=== Checking out code === | === Checking out code === | ||
- | As read-only access to the repository is not restricted in any ways, you can obtain a working copy of the source code by running | + | You can obtain a working copy of the source code by running |
- | <code bash> | + | * __using Subversion...__ |
- | svn co http://lus.lofar.org/ | + | svn co http://usg.lofar.org/ |
- | </ | + | * __using Git...__ <code bash> |
+ | git svn clone http:// | ||
+ | </ | ||
+ | git svn clone -r < | ||
+ | cd lofarsoft | ||
+ | git svn rebase | ||
+ | </ | ||
- | In case you not only want a working version of the source code, but also of the various documents, you do have two options to options of retrieval: | + | In case you not only want a working version of the source code, but also of the various documents:< |
- | - Check out everything in a single go: <code bash> | + | |
- | svn co http:// | + | |
- | </ | + | |
- | - Check out a slightly cleaned-up version, omitting the '' | + | |
mkdir usg | mkdir usg | ||
cd usg | cd usg | ||
- | svn co http://lus.lofar.org/ | + | svn co http://usg.lofar.org/ |
- | svn co http://lus.lofar.org/ | + | svn co http://usg.lofar.org/ |
</ | </ | ||
- | === Updating your working copy === | + | Note: Release versions of the Pulsar tools (as used on CEP2 and CEP3) can be obtained from the URL (for example):< |
- | + | svn co http:// | |
- | Go to the '' | + | |
- | < | + | |
- | make update | + | |
</ | </ | ||
- | In the simplest case this might be nothing but a wrapper around the '' | + | This will download |
- | Then build your target, for example " | + | === Bootstrapping |
- | <code bash> | + | |
- | make dal | + | Once the checkout from the central repository has completed, you are left with a directory structure as described above. The next step now is to get to the point where it is possible to build (and subsequently install) packages in the software collection... |
- | </code> | + | |
+ | As the LUS uses the CMake cross-platform makefile generator to handle the configuration of the code base, the most important thing to check is whether or not a suitable version of CMake is available on your platform -- this check is carried out through the bootstrap script in the top-level directory of the working copy: | ||
- | You can also just build the target folder leaving everything else untouched using | ||
<code bash> | <code bash> | ||
- | cd dal | + | ./bootstrap |
- | make rebuild_cache && make && make install | + | |
</ | </ | ||
+ | |||
+ | The the main job of the '' | ||
+ | |||
+ | === Updating your working copy === | ||
+ | |||
+ | As with the case of retrieving your working working copy from the central repository, this step is very much depending on the tool used locally for version control: | ||
+ | |||
+ | * __Subversion__ : Change back to the top-level directory of your working copy and and run <code bash>svn up</ | ||
+ | |||
+ | * __Git__ : Depending on your choice to deal with upstream changes, you might change back to the '' | ||
+ | git checkout master | ||
+ | git svn rebase | ||
+ | </ | ||
+ | |||
+ | ==== Local installation ==== | ||
+ | {{public: |