DAQ OS: front end libraries: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
All front end libraries are licated in ''$CODA/src/rol/code.s'' directory. To compile use gmake clean, gmake and gmake install. For vxWorks use clon10/clon00 servers only (it will work on RHEL as well, but historically we do it on sparc machines). | All front end libraries are licated in ''$CODA/src/rol/code.s'' directory. To compile use gmake clean, gmake and gmake install. For vxWorks use clon10/clon00 servers only (it will work on RHEL as well, but historically we do it on sparc machines). | ||
'''Generic software rules''' | '''Generic software development rules''' | ||
* | * Every board has distinctive name, for example v1495 or tdc1190. That name must be used in the files name, as well as in function names inside the files to avoid duplicate names. At least to files must be provided, for example v1495.c and v1495.h, where header file will be used in user readout lists. | ||
Revision as of 10:48, 14 April 2011
All front end libraries are licated in $CODA/src/rol/code.s directory. To compile use gmake clean, gmake and gmake install. For vxWorks use clon10/clon00 servers only (it will work on RHEL as well, but historically we do it on sparc machines).
Generic software development rules
- Every board has distinctive name, for example v1495 or tdc1190. That name must be used in the files name, as well as in function names inside the files to avoid duplicate names. At least to files must be provided, for example v1495.c and v1495.h, where header file will be used in user readout lists.