Version 7 (modified by 19 years ago) (diff) | ,
---|
Constructing a release for CMT
External dependencies
Doxygen
html2ps
Final step on the sources
The final step for preparing the release consists in
Files to be changed lastly are:
- cmt_version.h
- CMTDoc.xml
- requirements (only when major release changes)
Sequence is:
- Changing CMTDoc.xml (and requirements if needed) in HEAD
- svn copy to new tag
- Changing cmt_version.h in new tag only (stays "HEAD" in HEAD)
Build the binaries
Binaries are built on various machines, then copied to /lal/CMT/*/
VisualC | laptop |
CYGWIN_NT-5.1-i686 | laptop |
OSF1-alpha | asc |
Linux-i686 | lxbuild002 |
Linux-x86_64 | atlas2.lal.in2p3 |
SunOS-sun4u | ccasn.in2p3.fr |
AIX-002064874C00 | ccars.in2p3.fr |
Build the documentations
- Run the documentation generators
gmake doxygen # on atlas.lal.in2p3.fr gmake gendoc # needs Python >= 2.3 gmake pdf # on lxplus
- Prepare ReleaseNotes.html form ChangeLog
- Prepare ../doc/download.html by installing the reference to the new version.
Build the pacman kit
gmake pacman cp CMT-<version>.pacman /www/Web/htdocs/cmtsite/pacman/cache
Export to the CMT Web site
gmake Export on a LAL machine cd ../../ rm CMT*