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-11-21 15:25] – Lars Bahren | public:user_software:user_software [2017-03-08 15:27] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== LOFAR User Software ====== | ====== LOFAR User Software ====== | ||
| + | |||
| + | < | ||
| + | <div style=" | ||
| + | </ | ||
| __TOC__: | __TOC__: | ||
| Line 13: | Line 17: | ||
| * [[CR-Tools]] | * [[CR-Tools]] | ||
| * [[DAL|Data Access Library]] (DAL) | * [[DAL|Data Access Library]] (DAL) | ||
| + | * [[http:// | ||
| * [[LOPES-Eventbrowser]] | * [[LOPES-Eventbrowser]] | ||
| - | * [[pyBDSM]] | + | * <del>[[pyBDSM]]</ |
| - | * [[PyCRTools]] | + | * [[http:// |
| * [[Pulsar Tools]] | * [[Pulsar Tools]] | ||
| + | * < | ||
| + | - [[Building an individual package]] | ||
| - [[# | - [[# | ||
| - [[Reorganization of the software collection]] | - [[Reorganization of the software collection]] | ||
| Line 29: | Line 36: | ||
| | |-- branches | | |-- branches | ||
| | `-- trunk | | `-- trunk | ||
| - | | | + | | |
| | | | | ||
| | | | | ||
| Line 40: | 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 |
| * __using Subversion...__ <code bash> | * __using Subversion...__ <code bash> | ||
| - | svn co http:// | + | svn co http:// |
| - | </ | + | |
| * __using Git...__ <code bash> | * __using Git...__ <code bash> | ||
| - | git svn clone http:// | + | git svn clone http:// |
| </ | </ | ||
| - | git svn clone -r < | + | git svn clone -r < |
| cd lofarsoft | cd lofarsoft | ||
| git svn rebase | 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 | ||
| Line 63: | Line 65: | ||
| </ | </ | ||
| + | Note: Release versions of the Pulsar tools (as used on CEP2 and CEP3) can be obtained from the URL (for example):< | ||
| + | svn co http:// | ||
| + | </ | ||
| + | This will download the whole tree, including the pulsar tools. | ||
| - | === Updating | + | === Bootstrapping |
| - | Go to the '' | + | 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 bash> | + | |
| - | make update | + | |
| - | </ | + | |
| - | In the simplest case this might be nothing but a wrapper around the '' | + | |
| - | Then build your target, for example " | + | 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: |
| - | <code bash> | + | |
| - | make dal | + | |
| - | </ | + | |
| - | 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 | + | |
| </ | </ | ||
| - | === Write access | + | The the main job of the '' |
| - | FIXME < | + | |
| - | While (by design) the user software repository is world-wide readable, write access is being restricted to a list of registered users. The basic procedure for getting added to that list -- which basically relies on a combination of a '' | + | === Updating your working copy === |
| - | The information which needs to be provided by the user is a combination | + | 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: |
| - | * Using '' | + | * __Subversion__ |
| - | * Using '' | + | |
| - | If none of the above mentioned tools are available, use can be made of an [[http:// | + | * __Git__ |
| - | + | git checkout master | |
| - | Depending on the command line tool being used, the output will contain the full string | + | git svn rebase |
| - | <file> | + | </code> If however you prefer to directly merge the upstream changes into your feature/ |
| - | lbaehren: | + | |
| - | $apr1$9H8IBSvy$yswI9jLosDkDx1a6.12345 | + | |
| - | </file> | + | |
| - | + | ||
| - | ==== Supported platforms ==== | + | |
| - | + | ||
| - | First-level supported platforms: | + | |
| - | + | ||
| - | | + | |
| - | Second-level supported platforms: | ||
| - | - Debian GNU/Linux 6.x | ||
| + | ==== Local installation ==== | ||
| + | {{public: | ||