Difference between revisions of "Common mca2 scripts"

From Mca2
Jump to navigationJump to search
(copied parts of docbook chapter on coding standards)
 
(One intermediate revision by one other user not shown)
Line 3: Line 3:
 
== create file templates ==
 
== create file templates ==
 
* newPart
 
* newPart
{{cmd|[~]$ newPart base_path name}}
+
<pre>
 +
  [~]$ newPart base_path name
 +
</pre>
 
Creates a new part. The .C file is created with the given name in the $MCAHOME/base_path/src subdirectory. A 'p' is automatically prepended. No header file is generated.
 
Creates a new part. The .C file is created with the given name in the $MCAHOME/base_path/src subdirectory. A 'p' is automatically prepended. No header file is generated.
  
  
 
*newGroup  
 
*newGroup  
{{cmd|[~]$ newGroup base_path name}}
+
<pre>
 +
  [~]$ newGroup base_path name
 +
</pre>
 
Creates a new group. Parameters are evalulated like in the newPart script. A 'g' is automatically prepended to the given name. Additional to the .C file, a header file is created in $MCAHOME/base_path/include.
 
Creates a new group. Parameters are evalulated like in the newPart script. A 'g' is automatically prepended to the given name. Additional to the .C file, a header file is created in $MCAHOME/base_path/include.
  
  
 
* newModule  
 
* newModule  
{{cmd|[~]$ newModule base_path name}}
+
<pre>
 +
  [~]$ newModule base_path name
 +
</pre>
 
Creates a new module. A 'm' is automatically prepended to the given name. Both .C and .h files are created.
 
Creates a new module. A 'm' is automatically prepended to the given name. Both .C and .h files are created.
  
  
 
*newClass  
 
*newClass  
{{cmd|[~]$ newClass base_path name}}
+
<pre>
 +
  [~]$ newClass base_path name
 +
</pre>
 
Creates a new class. A 't' is automatically prepended to the given name. Both .C and .h files are created.
 
Creates a new class. A 't' is automatically prepended to the given name. Both .C and .h files are created.
  
  
 
*newStaticClass  
 
*newStaticClass  
{{cmd|[~]$ newStaticClass base_path name}}
+
<pre>
 +
  [~]$ newStaticClass base_path name
 +
</pre>
 
Creates a new static class. A 's' is automatically prepended to the given name. Both .C and .h files are created.
 
Creates a new static class. A 's' is automatically prepended to the given name. Both .C and .h files are created.
  

Latest revision as of 15:03, 2 July 2010

TODO: up to now just a list of used scripts

create file templates

  • newPart
  [~]$ newPart base_path name

Creates a new part. The .C file is created with the given name in the $MCAHOME/base_path/src subdirectory. A 'p' is automatically prepended. No header file is generated.


  • newGroup
  [~]$ newGroup base_path name

Creates a new group. Parameters are evalulated like in the newPart script. A 'g' is automatically prepended to the given name. Additional to the .C file, a header file is created in $MCAHOME/base_path/include.


  • newModule
  [~]$ newModule base_path name

Creates a new module. A 'm' is automatically prepended to the given name. Both .C and .h files are created.


  • newClass
  [~]$ newClass base_path name

Creates a new class. A 't' is automatically prepended to the given name. Both .C and .h files are created.


  • newStaticClass
  [~]$ newStaticClass base_path name

Creates a new static class. A 's' is automatically prepended to the given name. Both .C and .h files are created.

empty templates for these scripts are in etc/Null...

create a new release

  • make-release
  • test-release

transfer files to a second host

  • synchronize.py
  • sync.py

set environment vairables

  • mcasetenv.bat (Windows only)
  • mcasetenv (bash script)
  • mcasetenv.py (phyton script used by mcasetenv)