public:user_software:cr-tools:organization_of_the_source_code

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

public:user_software:cr-tools:organization_of_the_source_code [2011-10-18 12:22] – created Lars Bahrenpublic:user_software:cr-tools:organization_of_the_source_code [2011-10-18 18:25] (current) – removed Lars Bahren
Line 1: Line 1:
-===== User Software :: CR-Tools :: Organization of the source code ====== 
- 
-{{ :public:user_software:core_tree_usg_repository.png|}} 
- 
-After the check-out -- which will take a while -- you will be left with a new directory tree organized as follows: 
- 
-  * **usg** is the root of the User Software code tree -- go there if you want to synchronize your local version against the repository. 
-  * **build** is used for building individual packages in the code distribution; using a separate directory for this purpose makes it easy to simply erase all compile and link attempts and start again from a clean plate. 
-  * **devel_common** hold common tools for development; this includes e.g. the find scripts for CMake or file templates for creating new C++ classes. Unless you consider collaborating on the framework, you will not need to touch this (but you will need it). 
-  * **doc** contains a local version of the Doxygen-based source code documentation; just go in there, fire up Doxygen and get an up-to-date version of the source code documentation. 
-  * **external** hosts the various external packages which will be required to build parts of the LOFAR User Software; the main change her w.r.t. to old LOPES-Tools is, that critical components are distributed along with the stuff we are writing ourselves. This directory also contains **casacore**, a collection of the core libraries of the **CASA** system. 
- 
  
  • Last modified: 2011-10-18 12:22
  • by Lars Bahren