Difference: AMC13CppSoftwareBuildNotes (10 vs. 11)

Revision 1114 May 2013 - CharlieHill

Line: 1 to 1

META TOPICPARENT	name="HcalDTC"

The following procedures describe the installation process for xDAQ releases for the HCAL Upgrade project. NOTE that the code has been migrated to SVN (instead of CVS) as of 02/07/2013, hence these instructions have since then been updated.

Line: 7 to 7

NOTE!!! These examples show how to install release 11_8_1, but the process can be generalized to any xDAQ release xx_x_x.

Contents

Changed:

<
<

Install a Releast as daqowner

>
>

Install a Release as daqowner

Install a release in your own source tree

Check edited code back into SVN

Subscribe to HCAL Online Software HyperNews

Line: 89 to 89

If you want to check the xDAQ code out of SVN anonymously (i.e. if you do not have an afs ID or don't care to have access to the repository), edit the script, search for "anonymous", and remove the # comment mark. Otherwise, if you have an afs ID and want access to the repository, skip this step.
Run the installation script, ownsourcing the code to your ${HOME}/src directory:

Changed:

<
< perl ~/installDAQ_11_8_1.perl --mode-teststand --ownsource=${HOME}/src/11_8_1 --packages=hcalUpgrade svnuser=[afsID]

>
> perl ~/installDAQ_11_8_1.perl --mode=teststand --ownsource=${HOME}/src/11_8_1 --packages=hcalUpgrade svnuser=[afsID]

- NOTE that you can put the code into any directory you like; it doesn't have to be ${HOME}/src/11_7_7.
- NOTE that you can also install additional packages, if you wish; you're not limited to the hcalUpgrade. However, ALL of the AMC13 code lies within the hcalUpgrade package!! If packages is not specified, then all packages are installed by default.

Added:

>
>

- NOTE that the uHTR code is in the hcalUHTR package

- NOTE that if you removed the "anonymous" comment mark in the previous step, you do not need the svnuser argument.

Set the environment for your new ownsource code development area:
```
   source /home/daqowner/dist/etc/env.sh
```

Changed:

<
< export LD_LIBRARY_PATH=${HOME}/src/11_7_7/hcal/hcalUpgrade/amc13/lib/linux/x86_64_slc5/:${LD_LIBRARY_PATH}

>
> export LD_LIBRARY_PATH=${HOME}/src/11_8_1/hcal/hcalUpgrade/amc13/lib/linux/x86_64_slc5/:${LD_LIBRARY_PATH}

If you provided your "svnuser" afs ID (and therefore have access to the repository), update the software to the latest code in SVN (in case changes have been checked in by other parties since this release):

Changed:

<
< cd ~/src/11_7_7/hcal/hcalUpgrade/

>
> cd ~/src/11_8_1/hcal/hcalUpgrade/

svn update

Build the code in exactly the following order:

Changed:

<
< cd ~/src/11_7_7/hcal/hcalUpgrade/ipbus/

>
> cd ~/src/11_8_1/hcal/hcalUpgrade/ipbus/

make cd ../amc13 make

Line: 115 to 116

After the code is done building, you have finished! You are now ready to run the AMC13Tool executable and edit your private development area!

Changed:

<
< If you wish to edit the AMC13 code, you can make changes to the source code in ${HOME}/src/11_7_7/hcal/hcalUpgrade/amc13/src/common/ and then go back up to the /amc13 level to recompile using make.

>
> If you wish to edit the AMC13 code, you can make changes to the source code in ${HOME}/src/11_8_1/hcal/hcalUpgrade/amc13/src/common/ and then go back up to the /amc13 level to recompile using make.

Check edited code back into SVN

If you have edited the AMC13 code and want to make the edits available to other developers (important for bug fixes!), you will need to check your changes back into SVN. If you are unfamiliar with SVN, it is a good idea to take a quick gander at the Subversion Manual

before proceeding. For a more succinct look at the basic SVN commands, check out this site

Changed:

<
< IMPORTANT!!! It is imperative that you make sure your edited code compiles and runs without breaking before checking changes into SVN. the HCAL Upgrade does not want to release busted software!

>
> IMPORTANT!!! It is imperative that you make sure your edited code compiles and runs without breaking before checking changes into SVN. The HCAL Upgrade does not want to release busted software!

Go to the hcal/hcalUpgrade level of the release directory and svn update:

View topic | History: r26 < r25 < r24 < r23 | More topic actions...