| Version 2 (modified by , 21 years ago) ( diff ) |
|---|
Constructing a release for CMT
Final step on the sources
The final step for preparing the release consists in
- changing cmt_version.h
- checking in to SVN (still at HEAD)
Building 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 |
- Check that once copied to LAL, all cmt.exe are executable
- Remove *.o files before creating the tar balls
- Create the symlinks cmt -> cmt.exe
Building 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
Exporting to the CMT Web site
gmake Export on a LAL machine cd ../../ rm CMT*
Final SVN tagging
Note:
See TracWiki
for help on using the wiki.
