Difference between revisions of "Online release"
m |
|||
| Line 2: | Line 2: | ||
| − | Official online releases must be made from the hdsys account. You can make a release in your own area | + | Official online releases must be made from the hdsys account. You can also make a release in your own area: |
| − | 1. | + | 1. For official releases log into the hdsys account on the Hall D online computing cluster and cd to the release area. If you don't know how to do this then you should not be making official releases! If you are just making a private release then log into your own account and cd to wherever you want to make the release. |
| Line 13: | Line 13: | ||
usage: | usage: | ||
| − | create_online_release [-noBuild] [-noCheckout] [-noCPP] [-noJava] [-noInstall] | + | create_online_release releaseName [-noBuild] [-noCheckout] [-noCPP] [-noJava] [-noInstall] |
| Line 30: | Line 30: | ||
| − | 5. Create release | + | 5. Create release in current working directory, check out all packages, build and install everything |
$ create_online_release myRelease | $ create_online_release myRelease | ||
Revision as of 11:27, 20 May 2013
How To Make an Online Release
Official online releases must be made from the hdsys account. You can also make a release in your own area:
1. For official releases log into the hdsys account on the Hall D online computing cluster and cd to the release area. If you don't know how to do this then you should not be making official releases! If you are just making a private release then log into your own account and cd to wherever you want to make the release.
2. Get a copy of the release script:
$ svn cat https://halldsvn.jlab.org/repos/trunk/online/packages/buildScripts/scripts/create_online_release > create_online_release usage: create_online_release releaseName [-noBuild] [-noCheckout] [-noCPP] [-noJava] [-noInstall]
3. Set PATH to point to gcc 4.8.0 (or whatever compiler you want) and set LD_LIBRARY_PATH accordingly:
$ setenv PATH /apps/gcc/4.8.0/bin:"$PATH" $ setenv LD_LIBRARY_PATH /apps/gcc/4.8.0/lib64:/apps/gcc/4.8.0/lib:"$LD_LIBRARY_PATH"
4. Set environment variables needed for the build. We are working on a script to do this, until then:
$ setenv CMSGROOT /gluex/coda_install_dir/Linux-x86_64 $ setenv EVIOROOT /gluex/coda_install_dir/Linux-x86_64 $ setenv ETROOT /gluex/coda_install_dir/Linux-x86_64 $ setenv CODAOBJECTROOT /gluex/coda_install_dir/Linux-x86_64
5. Create release in current working directory, check out all packages, build and install everything
$ create_online_release myRelease
