Difference: WindowsDevEnv (1 vs. 34)

Revision 342011-10-12 - PatrickSKoppenburg

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Added:
>
>
Official windows support was dropped in October 2011. All what is below is likely to be obsolete.
 These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (cerntslhcb03.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections. To request the rights to log on to this machine please contact Joel.Cloiser AT cern.ch.

In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris. The lhcbts installation is maintained by Hubert.

Revision 332011-06-17 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 125 to 125
 
  1. add the customisations.
  2. change the LOGIN_POST_SCRIPT variable in the system properties to point to D:\Profiles\degauden\mysetup (the .bat extension is automatically added)
Added:
>
>
More exhaustive informations about the behavior of the the login procedure can be found in the LbScripts release web pages
 

Local installation of LHCb software

  • Every release of the LHCb software is installed on the local disk of the terminal server (in E:\soft) by the LHCb software librarian, using the install_project.py script
Line: 146 to 148
  Hint: If you have a desktop shortcut to start a terminal window, you can modify its properties to execute the script automatically: right-click on the icon, select Properties, Shortcut tab. In "Target:" append the string: /K %MYSITEROOT%\LbLogin.bat & "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\vsvars32.bat". In "Start in:" you could choose to start in %User_release_area%.
Added:
>
>
Alternatively you can also use the LOGIN_POST_SCRIPT feature to call the compiler setup. The entry in the short cut tab stays:
       C:\WINNT\system32\cmd.exe /k %VO_LHCB_SW_DIR%\lib\LbLogin.bat 
and the script %LOGIN_POST_SCRIPT%.bat is called automatically (please see above)
 

Available Commands at the DOS Prompt

Revision 322011-06-17 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 114 to 114
 The official software releases against which you build your software can be either installed on the local disk of the Windows machine (recommended) or accessed from the central AFS installation (slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally). By analogy with working on Linux, commands to check out, build and run the LHCb software are executed in a DOS terminal window, in which the LHCb environment has been set (via execution of a "login" script). Different scripts are executed depending on whether you choose to work with the local installation or the AFS installation.

Pre-defined terminal windows on the LHCb terminal server

Changed:
<
<
When you log in to the LHCb terminal server, you will find two terminal icons. These shortcuts provide a shell with the CMT environment set up for usage of either the local LHCb software installation on the machine ("LHCb local" icon) or the AFS software installation ("LHCb AFS" icon). Double click on one of these icons to open a terminal window
>
>
When you log in to the LHCb terminal server, you will find two terminal icons. These shortcuts provide a shell with the CMT environment set up for usage of either the local LHCb software installation on the machine ("Lblogin local" icon) or the AFS software installation ("LbLogin AFS" icon). Double click on one of these icons to open a terminal window.

These shortcuts are calling different instances of the LbLogin.bat script setting up different software locations. But both of them are calling a local post setup script %LOGIN_POST_SCRIPT%.bat if it exists. On the LHCb windows terminal servers, The LOGIN_POST_SCRIPT variable is defined system-wide and it is pointing to %LOCALINSTALLDRIVE%\local\lib\studio. This later bat script is then calling the proper compiler setup.

The user can also use that variable to customize the post setup of the login procedure. In order to do this, she/he has to (for example):

  1. create a new script (D:\Profiles\degauden\mysetup.bat) containing a call to the orginal studio.bat
         call  %LOCALINSTALLDRIVE%\local\lib\studio.bat 
  1. add the customisations.
  2. change the LOGIN_POST_SCRIPT variable in the system properties to point to D:\Profiles\degauden\mysetup (the .bat extension is automatically added)
 

Local installation of LHCb software

  • Every release of the LHCb software is installed on the local disk of the terminal server (in E:\soft) by the LHCb software librarian, using the install_project.py script

Revision 312011-06-14 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Changed:
<
<
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (cerntslhcb01.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections. To request the rights to log on to this machine please contact Joel.Cloiser AT cern.ch.
>
>
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (cerntslhcb03.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections. To request the rights to log on to this machine please contact Joel.Cloiser AT cern.ch.
  In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris. The lhcbts installation is maintained by Hubert.
Line: 61 to 61
 
Register your CERN NICE account for TS access
You should subscribe to the e-group called "lhcb-ts-users".
Changed:
<
<
Start a session on the terminal server cerntslhcb01.cern.ch.
>
>
Start a session on the terminal server cerntslhcb03.cern.ch.
 
  • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Changed:
<
<
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntslhcb01.cern.ch
>
>
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntslhcb03.cern.ch
 
  • Connection Problems ?
    • If you experience problems connecting to the Terminal Server from outside CERN, it is possible that your local network is blocking connections through the RDP port 3389. Symptoms are, for example with rdesktop :-

Changed:
<
<
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntslhcb01.cern.ch
>
>
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntslhcb03.cern.ch
 pcdn ~ > ERROR: connect: Connection refused
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.

Revision 302011-03-02 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 78 to 78
 

Completing the installation

This section describes actions needed by all users both on standalone PCs and the Terminal Server. To set environment variables, use Start->Control Panel->System->Advanced Menu
Changed:
<
<
Configure SSH access to the CVS repository
  • Detailed instructions can be found here.
>
>
Configure SSH access to the SVN repository
  • Detailed instructions can be found here (and here for CVS [obsolete]).
 
  • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. Without administrator rights it is still possible to use "Startup scripts":
    • "right click" on Start button, and "Open" in the context menu
    • Navigate to: Programs\Startup
Line: 91 to 91
 
    • Where <path-to-private-key> is the complete path to your private ssh key.
    • Double clicking this new icon will start up pagent and add you key.
    • If the SSH configuration was successful, you should be able to connect without password with only the private/public key verification. In order to check this, you can try:
Changed:
<
<
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
>
>
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@svn.cern.ch
  where (username) is the lxplus account you have used to set up your ssh key.
Changed:
<
<
    • Define the environment variables CVSROOT = ":ext:isscvs.cern.ch:/local/reps/lhcb" and CVS_RSH must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".
>
>
    • [obsolete, only for CVS access] Define the environment variables CVSROOT = ":ext:isscvs.cern.ch:/local/reps/lhcb" and CVS_RSH must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".
 
Define a User_release_area
The User_release_area environment variable must be defined to point to a read/write directory. This will be your working directory and, for speed of access reasons, it is recommended to set it up on a local disk (though remember that it is then up to you to back it up)

Revision 292011-01-18 - JoelClosier

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 59 to 59
 
  • Note - rdesktop has already been installed in the Scientific Linux CERN distribution.

Register your CERN NICE account for TS access
Changed:
<
<
This can also be done from here.
>
>
You should subscribe to the e-group called "lhcb-ts-users".
 
Start a session on the terminal server cerntslhcb01.cern.ch.
  • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Revision 282010-10-12 - OlivierCallot

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 59 to 59
 
  • Note - rdesktop has already been installed in the Scientific Linux CERN distribution.

Register your CERN NICE account for TS access
Changed:
<
<
This can also be done from here.
>
>
This can also be done from here.
 
Start a session on the terminal server cerntslhcb01.cern.ch.
  • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Revision 272010-03-19 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 80 to 80
 
Configure SSH access to the CVS repository
  • Detailed instructions can be found here.
Changed:
<
<
  • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
>
>
  • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. Without administrator rights it is still possible to use "Startup scripts":
    • "right click" on Start button, and "Open" in the context menu
    • Navigate to: Programs\Startup
    • Create a new shortcut in this directory with Target action set as: "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key>

  • Another work around of Scheduled Tasks is to create a desktop short cut :
 
    • Create a new shortcut on your desktop (right click on the desktop)
    • Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key>
    • Where <path-to-private-key> is the complete path to your private ssh key.
Line: 197 to 202
 
The Eclipse IDE 3.3 (Europa)
with support for Python and C++ development. See EclipseConfiguration
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
Added:
>
>
-- KarolKruzelecki - 19-Mar-2010
 -- MarcoCattaneo - 29 May 2009 -- HubertDegaudenzi - 11 Jul 2008 -- ChristopherRJones - 20 Dec 2007

Revision 262009-10-08 - ChristopherRJones

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Changed:
<
<
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (cerntslhcb01.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections.
>
>
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (cerntslhcb01.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections. To request the rights to log on to this machine please contact Joel.Cloiser AT cern.ch.
  In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris. The lhcbts installation is maintained by Hubert.
Line: 61 to 61
 
Register your CERN NICE account for TS access
This can also be done from here.
Changed:
<
<
Start a session on the terminal server lhcbts.cern.ch.
>
>
Start a session on the terminal server cerntslhcb01.cern.ch.
 
  • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Changed:
<
<
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" lhcbts.cern.ch
>
>
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntslhcb01.cern.ch
 
  • Connection Problems ?
    • If you experience problems connecting to the Terminal Server from outside CERN, it is possible that your local network is blocking connections through the RDP port 3389. Symptoms are, for example with rdesktop :-

Changed:
<
<
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" lhcbts.cern.ch
>
>
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntslhcb01.cern.ch
 pcdn ~ > ERROR: connect: Connection refused
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.

Revision 252009-08-31 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 23 to 23
 
  • For a local installation (recommended):
    • Create a directory on the local disk under which you will install the software. e.g. C:\releases
    • In Start->Control Panel->System->Advanced Menu, define the environment variable MYSITEROOT to point to the above directory
Changed:
<
<
>
>
 
      • Get an AFS token via the Network Identity Manager (icon installed by step 3 in your system tray), not via the AFS Client
      • Follow the step 6 instructions, but adding a network place with name AFS and network address \\10.254.254.253\all
    • In Windows Explorer -> Tools -> Map network drive:

Revision 242009-07-29 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Changed:
<
<
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (lhcbts.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections.
>
>
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (cerntslhcb01.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections.
  In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris. The lhcbts installation is maintained by Hubert.

Revision 232009-06-24 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 194 to 194
  Beside the Windows Visual C++ development tools, a bunch of other development tools have also been installed on LHCbTS:
Some editors
Vim, Emacs, XEmacs
Changed:
<
<
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
>
>
The Eclipse IDE 3.3 (Europa)
with support for Python and C++ development. See EclipseConfiguration
 
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.

-- MarcoCattaneo - 29 May 2009

Revision 222009-05-29 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 111 to 111
 

Pre-defined terminal windows on the LHCb terminal server

When you log in to the LHCb terminal server, you will find two terminal icons. These shortcuts provide a shell with the CMT environment set up for usage of either the local LHCb software installation on the machine ("LHCb local" icon) or the AFS software installation ("LHCb AFS" icon). Double click on one of these icons to open a terminal window
Deleted:
<
<

Setting up a terminal window on a standalone machine

Start a terminal window (Start->Run..->cmd), then execute a script equivalent to the group login on Linux, to set up all other environment variables necessary to work with CVS and CMT. Depending on whether or not you have installed the software locally, you should type:

  • %MYSITEROOT%\scripts\localsetup.bat (local installation)
  • Z:\cern.ch\lhcb\scripts\win32\lhcbsetup (AFS installation)

(Hint: If you have a desktop shortcut to start a terminal window, you can modify its properties to execute the script automatically: right-click on the icon, select Properties, Shortcut tab. In "Target:" append the string: /K Z:\cern.ch\lhcb\scripts\win32\lhcbsetup. In "Start in:" you could choose to start in %User_release_area%.)

 

Local installation of LHCb software

  • Every release of the LHCb software is installed on the local disk of the terminal server (in E:\soft) by the LHCb software librarian, using the install_project.py script
  • On a standalone PC, you have to install yourself at least one version of the LHCb software stack, using the installProject.py script.
Changed:
<
<
Import the software by following the instructions given here.
>
>
Import the software by following the instructions given here.
 

Using the AFS release area

In order to be able to access the AFS volumes, you have to setup your OpenAFS token (Start->All Programs->OpenAFS->Client->authentication)
Added:
>
>

Setting up the LHCb environment terminal window on a standalone machine

Start a terminal window (Start->Run..->cmd), then execute a script equivalent to the group login on Linux, to set up all other environment variables necessary to work with CVS and CMT. Depending on whether or not you have installed the software locally, you should type:

  • %MYSITEROOT%\LbLogin.bat (local installation)
  • Z:\cern.ch\lhcb\software\releases\LBSCRIPTS\prod\InstallArea\scripts\LbLogin.bat (AFS installation)

You then have to set up the environment for the compiler, with the command:

  • "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\vsvars32.bat" (Mandatory, C++)
  • "C:\Program Files\Microsoft Visual Studio\DF98\BIN\DFVARS.BAT" (Optional, if you have also installed the Fortran compiler)

Hint: If you have a desktop shortcut to start a terminal window, you can modify its properties to execute the script automatically: right-click on the icon, select Properties, Shortcut tab. In "Target:" append the string: /K %MYSITEROOT%\LbLogin.bat & "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\vsvars32.bat". In "Start in:" you could choose to start in %User_release_area%.

 

Available Commands at the DOS Prompt

(Hint: If you want to have a unix shell style "tab" behaviour to autocomplete a filename/directory in DOS, set the value "9" in the registry key:

Line: 192 to 197
 
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
Changed:
<
<
-- MarcoCattaneo - 24 Oct 2008
>
>
-- MarcoCattaneo - 29 May 2009
 -- HubertDegaudenzi - 11 Jul 2008 -- ChristopherRJones - 20 Dec 2007 -- DavidHutchcroft - 22 Feb 2008

Revision 212009-01-22 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 20 to 20
 
Prepare access to the LHCb software releases
You have to decide whether to install all the LHCb software locally (recommended) or access the centrally maintained LHCb software release area in AFS
Changed:
<
<
  • For a local installation:
>
>
  • For a local installation (recommended):
 
    • Create a directory on the local disk under which you will install the software. e.g. C:\releases
    • In Start->Control Panel->System->Advanced Menu, define the environment variable MYSITEROOT to point to the above directory
Changed:
<
<
  • For AFS access, install OpenAFS
    • Installation instructions can be found here.
>
>
  • For AFS access, install OpenAFS. You need OpenAFS 1.5.39 or later for Kerberos 5 access, mandatory at CERN from February 2009
    • Follow carefully the instructions given in https://dfs.cern.ch/dfs/Applications/IBM/OpenAFS-1.5.39/CERNREADME.txt up to step 5. Then:
      • Get an AFS token via the Network Identity Manager (icon installed by step 3 in your system tray), not via the AFS Client
      • Follow the step 6 instructions, but adding a network place with name AFS and network address \\10.254.254.253\all
    • In Windows Explorer -> Tools -> Map network drive:
      • mandatory: Z: points to AFS
      • recommended: U: points to your AFS home directory, e.g. AFS\cern.ch\user\c\cattanem
 
    • Start the OpenAFS->Client->Authentication program, then click on the padlock in the system tray:
      • In Advanced Menu->Configure AFS Client->Drive letters:
        • Mandatory : Mount /afs as Z:
        • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
Added:
>
>
      • In Advanced Menu->Configure AFS Client->Advanced:
        • Recommended: Increase the size of your AFS cache (e.g. 1,000,000 kB cache and 10000 entries in Status Cache)
 
    • In Start->Control Panel->System->Advanced Menu, define the environment variable AFSROOT. It should be set to Z:

Install Microsoft Visual Studio .NET

Revision 202008-10-24 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 127 to 127
  The following commands are available at the DOS prompt:
Changed:
<
<
  • getpack Similar behaviour than the Linux one with the same arguments. It does the checkout from the cvs repository and configures the package.
  • setenvProject Setup your environment for a particular project (e.g. setenvProject Brunel v31r7). Wildcard usage does not always work - you may need to specify the version you want at the command line.
>
>
  • getpack Similar behaviour to the Linux one with the same arguments. It does the checkout from the cvs repository and configures the package.
  • SetupProject Setup your environment for a particular project (e.g. SetupProject Brunel v33r3).
 
  • cmt All cmt commands are available. This include the cmt broadcast, cmt checkout, etc.
Deleted:
<
<
  • setup To execute the setup.bat in each package to set the necessary environment variables.
 
  • make Is equivalent to "nmake /f nmake" (NB : This command is only available once you have run the setup.bat script from your application cmt directory).
  • cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain).
  • doxygen Wrapper for the doxygen documentation tool. See here for details.
Line: 142 to 141
  The following command sequence should just do the work of building and running (e.g. using Brunel)
Changed:
<
<
> setenvProject Brunel v32r2 > getpack Rec/Brunel v32r2 > cd Rec\Brunel\v32r2\cmt > setup.bat (needed in order for 'make' to work)
>
>
> SetupProject --build-env Brunel v33r3 > getpack Rec/Brunel v33r3 > cd Rec\Brunel\cmt
  > cmt make (or "cmt broadcast cmt make" for multiple packages)
Changed:
<
<
> cmt run ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts
>
>
> cmt run gaudirun ..\options\Brunel-Default.py .\someFiles.py
 
Added:
>
>
(Note that the command is gaudirun, not gaudirun.py)
 

Using Visual Studio .NET

Line: 156 to 155
  Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:
Changed:
<
<
> cd C:\cmtuser\Brunel_v32r2\Rec\Brunel\v32r2\cmt > setup
>
>
> cd C:\cmtuser\Brunel_v33r3\Rec\Brunel\cmt > SetupProject Brunel v33r3
  > cmt build vsnet > ..\Visual\Brunel.sln

The last command starts Visual Studio.NET. Before running e.g. Brunel, you may have to tell Visual Studio.NET about the job options file that you want to read:

Changed:
<
<
  • In Solution Explorer select Brunel
>
>
  • In Solution Explorer select all
 
  • In Project Menu: "Set as StartUp Project"
  • In Project Menu -> Properties...
    • Select Debugging the left hand panel
Changed:
<
<
    • In Command Arguments add: ..\options\v200601.opts
>
>
    • In Command add: python.exe
    • In Command Arguments add: C:\software\releases\lhcb\GAUDI\GAUDI_v20r2\InstallArea\scripts\gaudirun.py ..\options\Brunel-Default.py .\someFiles.py
(you need the full path to gaudirun.py, you can get it with which gaudirun.py in the DOS window)
  N.B. This step is only necessary once, it is remembered in subsequent Visual Studio.NET sessions with this executable
Line: 184 to 185
 
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
Added:
>
>
-- MarcoCattaneo - 24 Oct 2008
 -- HubertDegaudenzi - 11 Jul 2008
Deleted:
<
<
-- MarcoCattaneo - 19 Dec 2007
 -- ChristopherRJones - 20 Dec 2007
Changed:
<
<
- DavidHutchcroft - 22 Feb 2008
>
>
-- DavidHutchcroft - 22 Feb 2008
 
META FILEATTACHMENT attachment=".emacs" attr="" comment="An example '.emacs' file" date="1198148319" name=".emacs" path=".emacs" size="161" stream=".emacs" user="Main.ChristopherRJones" version="1"

Revision 192008-07-11 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 86 to 86
 
Define a User_release_area
The User_release_area environment variable must be defined to point to a read/write directory. This will be your working directory and, for speed of access reasons, it is recommended to set it up on a local disk (though remember that it is then up to you to back it up)
  • On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it
Changed:
<
<
  • On the terminal server, User_release_area is predefined to point to E:\users\(username)\cmtuser
>
>
  • On the terminal server, User_release_area is predefined to point to F:\users\(username)\cmtuser
 
  • It is also possible to define the User_release_area to be your AFS cmtuser directory. Set it to Z:\cern.ch\user\(u)\(username)\cmtuser
If necessary, define GETPACK_USER
The GETPACK_USER environment variable must be defined if your Windows username is different from your lxplus username. Set it to the lxplus username that you use to when working on LHCb.
Line: 146 to 146
  > getpack Rec/Brunel v32r2 > cd Rec\Brunel\v32r2\cmt > setup.bat (needed in order for 'make' to work)
Changed:
<
<
> make (or "cmt broadcast make" for multiple packages)
>
>
> cmt make (or "cmt broadcast cmt make" for multiple packages)
  > cmt run ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts
Line: 184 to 184
 
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
Changed:
<
<
-- HubertDegaudenzi - 30 Nov 2007
>
>
-- HubertDegaudenzi - 11 Jul 2008
 -- MarcoCattaneo - 19 Dec 2007 -- ChristopherRJones - 20 Dec 2007 - DavidHutchcroft - 22 Feb 2008

Revision 182008-02-22 - DavidHutchcroft

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 79 to 79
 
    • Where <path-to-private-key> is the complete path to your private ssh key.
    • Double clicking this new icon will start up pagent and add you key.
  • If the SSH configuration was successful, you should be able to connect without password with only the private/public key verification. In order to check this, you can try:
Changed:
<
<
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
       
where (username) is the lxplus account you have used to set up your ssh key.
>
>
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
where (username) is the lxplus account you have used to set up your ssh key.
    • Define the environment variables CVSROOT = ":ext:isscvs.cern.ch:/local/reps/lhcb" and CVS_RSH must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".
 
Define a User_release_area
The User_release_area environment variable must be defined to point to a read/write directory. This will be your working directory and, for speed of access reasons, it is recommended to set it up on a local disk (though remember that it is then up to you to back it up)
  • On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it
Line: 186 to 187
 -- HubertDegaudenzi - 30 Nov 2007 -- MarcoCattaneo - 19 Dec 2007 -- ChristopherRJones - 20 Dec 2007
Added:
>
>
- DavidHutchcroft - 22 Feb 2008
 
META FILEATTACHMENT attachment=".emacs" attr="" comment="An example '.emacs' file" date="1198148319" name=".emacs" path=".emacs" size="161" stream=".emacs" user="Main.ChristopherRJones" version="1"

Revision 172008-02-13 - ChristopherRJones

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 130 to 129
 
  • getpack Similar behaviour than the Linux one with the same arguments. It does the checkout from the cvs repository and configures the package.
  • setenvProject Setup your environment for a particular project (e.g. setenvProject Brunel v31r7). Wildcard usage does not always work - you may need to specify the version you want at the command line.
  • cmt All cmt commands are available. This include the cmt broadcast, cmt checkout, etc.
Deleted:
<
<
  • make Is equivalent to "nmake /f nmake"
 
  • setup To execute the setup.bat in each package to set the necessary environment variables.
Added:
>
>
  • make Is equivalent to "nmake /f nmake" (NB : This command is only available once you have run the setup.bat script from your application cmt directory).
 
  • cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain).
Changed:
<
<
  • doxygen Wrapper for the doxygen documentation tool. See here for details
>
>
  • doxygen Wrapper for the doxygen documentation tool. See here for details.
 
  • set Standard DOS command to set environment variables. Useful for setting variables for the current DOS window only. e.g. set User_release_area=C:\cmtuser

Building LHCb Software on Windows in Command Line Mode

Line: 145 to 144
  > setenvProject Brunel v32r2 > getpack Rec/Brunel v32r2 > cd Rec\Brunel\v32r2\cmt
Added:
>
>
> setup.bat (needed in order for 'make' to work)
  > make (or "cmt broadcast make" for multiple packages) > cmt run ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts

Revision 162007-12-20 - ChristopherRJones

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 95 to 95
 
      • Points to your "home" area (e.g. C:\Users\<username> on the TS). Used by emacs as the location to look for a ".emacs" file.
    • EMACSDIR
      • The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro"
Changed:
<
<
  • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
>
>
  • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here.
 

Accessing the LHCb software

The official software releases against which you build your software can be either installed on the local disk of the Windows machine (recommended) or accessed from the central AFS installation (slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally). By analogy with working on Linux, commands to check out, build and run the LHCb software are executed in a DOS terminal window, in which the LHCb environment has been set (via execution of a "login" script). Different scripts are executed depending on whether you choose to work with the local installation or the AFS installation.
Line: 183 to 183
 
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
Deleted:
<
<
-- HubertDegaudenzi - 30 Nov 2007, MarcoCattaneo - 19 Dec 2007
 \ No newline at end of file
Added:
>
>
-- HubertDegaudenzi - 30 Nov 2007 -- MarcoCattaneo - 19 Dec 2007 -- ChristopherRJones - 20 Dec 2007

META FILEATTACHMENT attachment=".emacs" attr="" comment="An example '.emacs' file" date="1198148319" name=".emacs" path=".emacs" size="161" stream=".emacs" user="Main.ChristopherRJones" version="1"

Revision 152007-12-20 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 151 to 151
 

Using Visual Studio .NET

Changed:
<
<
Note to Terminal Server Users : In order to use the graphical interface to Visual Studio .Net you need special access rights. You should ask Joel to add you to the "Debugger Users" group on the terminal server.
>
>
Note to Terminal Server Users : In order to use the graphical interface to Visual Studio .Net you need special access rights. You should ask Joel or Hubert to add you to the "Debugger Users" group on the terminal server.
 
Changed:
<
<
Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:
>
>
Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:
 
        > cd C:\cmtuser\Brunel_v32r2\Rec\Brunel\v32r2\cmt
        > setup

Revision 142007-12-19 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 13 to 13
  This section describes the software that has to be installed and configured on a standalone Windows machine. The instructions are given for machines in the CERN NICE environment. You can skip to the next section if you are using the Terminal Server, or if your PC was installed by the LHCb support team at CERN.
Changed:
<
<
Mandatory installations

  • Install the SSH application PuTTy
>
>
Install the SSH application PuTTy
SSH is needed to access the CERN CVS servers.
 
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
    • In Start->Control Panel->System->Advanced Menu, define the environment variable CVS_RSH. It must be set to the location of the PuTTy application plink. Normally this will be C:\Program Files\PuTTY\plink.exe.
Changed:
<
<
  • Install Microsoft Visual Studio .NET
>
>
Prepare access to the LHCb software releases
You have to decide whether to install all the LHCb software locally (recommended) or access the centrally maintained LHCb software release area in AFS
  • For a local installation:
    • Create a directory on the local disk under which you will install the software. e.g. C:\releases
    • In Start->Control Panel->System->Advanced Menu, define the environment variable MYSITEROOT to point to the above directory
  • For AFS access, install OpenAFS
    • Installation instructions can be found here.
    • Start the OpenAFS->Client->Authentication program, then click on the padlock in the system tray:
      • In Advanced Menu->Configure AFS Client->Drive letters:
        • Mandatory : Mount /afs as Z:
        • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
    • In Start->Control Panel->System->Advanced Menu, define the environment variable AFSROOT. It should be set to Z:

Install Microsoft Visual Studio .NET
 
    • On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005)
    • Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1
Changed:
<
<
  • Install the CERN Castor software
    • Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows.
>
>
Install the CERN Castor software
Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows.
 
    • On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC.
    • Otherwise you can try to download from here.
Changed:
<
<
Optional installations
  • OpenAFS
    • AFS is needed if you wish to access the centrally maintained LHCb software release area in AFS. In most cases it is more efficient to install the LHCb software stack locally (recommended).
    • If you choose to use AFS, installation instructions can be found here.
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
    • In Start->Control Panel->System->Advanced Menu, define the environment variable AFSROOT. It should be set to Z:
  • Emacs
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.
>
>
Install Emacs (optional)
If you are familiar with emacs and wish to use this on windows, follow the instructions here.
 

Preparing access to the Windows Terminal Server

This section describes the steps needed to access the LHCb Windows Terminal server for the first time. You can skip to the next section if you are using a standalone PC.
Changed:
<
<
  • Install the appropriate remote desktop software if needed
    • Installation instructions can be found from here for Windows, Mac and linux users.
>
>
Install the appropriate remote desktop software if needed
Installation instructions can be found from here for Windows, Mac and linux users.
 
      • Note - rdesktop has already been installed in the Scientific Linux CERN distribution.
Changed:
<
<
  • Register your CERN NICE account for TS access
    • This can also be done from here.
  • Start a session on the terminal server lhcbts.cern.ch.
>
>
Register your CERN NICE account for TS access
This can also be done from here.

Start a session on the terminal server lhcbts.cern.ch.
 
    • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is
       pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" lhcbts.cern.ch
Line: 63 to 71
 

Completing the installation

This section describes actions needed by all users both on standalone PCs and the Terminal Server. To set environment variables, use Start->Control Panel->System->Advanced Menu
Changed:
<
<
  • Define a User_release_area
    • The User_release_area environment variable must be defined to point to a read/write directory. This will be your working directory and, for speed of access reasons, it is recommended to set it up on a local disk (though remember that it is then up to you to back it up)
      • On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it
      • On the terminal server, User_release_area is predefined to point to E:\users\(username)\cmtuser
      • It is also possible to define the User_release_area to be your AFS cmtuser directory. Set it to Z:\cern.ch\user\(u)\(username)\cmtuser
  • If necessary, define GETPACK_USER
    • The GETPACK_USER environment variable must be defined if your Windows username is different from your lxplus username. Set it to the lxplus username that you use to when working on LHCb.
  • Configure SSH access to the CVS repository
>
>
Configure SSH access to the CVS repository
 
    • Detailed instructions can be found here.
Changed:
<
<
    • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
>
>
  • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
 
      • Create a new shortcut on your desktop (right click on the desktop)
      • Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key>
      • Where <path-to-private-key> is the complete path to your private ssh key.
Line: 81 to 82
 
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
       
where (username) is the lxplus account you have used to set up your ssh key.
Changed:
<
<
  • If you wish to use emacs:
>
>
Define a User_release_area
The User_release_area environment variable must be defined to point to a read/write directory. This will be your working directory and, for speed of access reasons, it is recommended to set it up on a local disk (though remember that it is then up to you to back it up)
  • On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it
  • On the terminal server, User_release_area is predefined to point to E:\users\(username)\cmtuser
  • It is also possible to define the User_release_area to be your AFS cmtuser directory. Set it to Z:\cern.ch\user\(u)\(username)\cmtuser
If necessary, define GETPACK_USER
The GETPACK_USER environment variable must be defined if your Windows username is different from your lxplus username. Set it to the lxplus username that you use to when working on LHCb.
If you wish to use emacs:
 
    • Define the following environment variables
      • HOME
        • Points to your "home" area (e.g. C:\Users\<username> on the TS). Used by emacs as the location to look for a ".emacs" file.
Line: 89 to 97
 
        • The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro" * Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
Changed:
<
<

Opening terminal windows

By analogy with working on Linux, commands to check out, build and run the LHCb software are executed in a DOS terminal window, in which the LHCb environment has been set (via execution of a "login" script).
>
>

Accessing the LHCb software

The official software releases against which you build your software can be either installed on the local disk of the Windows machine (recommended) or accessed from the central AFS installation (slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally). By analogy with working on Linux, commands to check out, build and run the LHCb software are executed in a DOS terminal window, in which the LHCb environment has been set (via execution of a "login" script). Different scripts are executed depending on whether you choose to work with the local installation or the AFS installation.
 

Pre-defined terminal windows on the LHCb terminal server

Changed:
<
<
When you log in to the LHCb terminal server, you will find two terminal icons. These shortcuts provide a shell with the CMT environment set up for usage of either the local LHCb software installation on the machine ("LHCb local" icon) or the AFS software installation ("LHCb AFS" icon)
>
>
When you log in to the LHCb terminal server, you will find two terminal icons. These shortcuts provide a shell with the CMT environment set up for usage of either the local LHCb software installation on the machine ("LHCb local" icon) or the AFS software installation ("LHCb AFS" icon). Double click on one of these icons to open a terminal window
 

Setting up a terminal window on a standalone machine

Added:
>
>
Start a terminal window (Start->Run..->cmd), then execute a script equivalent to the group login on Linux, to set up all other environment variables necessary to work with CVS and CMT. Depending on whether or not you have installed the software locally, you should type:
 
Changed:
<
<

LHCb software installations

The LHCb software is located in a cascade of distinct release areas. These normally consist of a read/write User_release_area, and one or more read only areas where the official releases are installed. Every release of the LHCb software stack is installed in AFS, and also one the local disk of the LHCb Terminal Server. Normally it is more efficient to use the local installation

Using locally installed releases

These instructions should be followed if you have chosen to use the local installation of the LHCb software stack (recommended)
>
>
  • %MYSITEROOT%\scripts\localsetup.bat (local installation)
  • Z:\cern.ch\lhcb\scripts\win32\lhcbsetup (AFS installation)
 
Changed:
<
<
  • On the terminal server, one of the icons on the desktop is called "LHCb Local". This shortcut provides a shell with your CMT environment set up for the usage of the local software installed on the machine (E:\soft). This software location has been installed with the install_project.py scripts and should contain the latest software releases of the LHCb projects
>
>
(Hint: If you have a desktop shortcut to start a terminal window, you can modify its properties to execute the script automatically: right-click on the icon, select Properties, Shortcut tab. In "Target:" append the string: /K Z:\cern.ch\lhcb\scripts\win32\lhcbsetup. In "Start in:" you could choose to start in %User_release_area%.)
 
Changed:
<
<
  • On a standalone PC, you have to install yourself at least one version of the LHCb software stack, using the installProject.py script.
    • Create a directory on the local disk under which you will install the software. e.g. C:\releases
    • Define the environment variable MYSITEROOT to point to the above directory
    • Import the software by following the instructions given here.
>
>

Local installation of LHCb software

  • Every release of the LHCb software is installed on the local disk of the terminal server (in E:\soft) by the LHCb software librarian, using the install_project.py script
  • On a standalone PC, you have to install yourself at least one version of the LHCb software stack, using the installProject.py script.
Import the software by following the instructions given here.
 

Using the AFS release area

Changed:
<
<
These instructions should be followed if you have chosen to use the AFS installation of the LHCb software stack. This method is slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally

As usual, in order to be able to access the AFS volumes, you have to setup your OpenAFS token (Start->All Programs->OpenAFS->Client->authentication).

  • On the terminal server, there is an icon on the desktop is called "LHCb AFS". This shortcut provides a shell with your CMT environment set up for the usage of the AFS software.

Map Network Drives (optional)

If you have chosen to use the AFS release area, and you are at CERN, we recommend that you map the directory \\cern.ch\dfs\Experiments to the S: drive. This directory contains a collection of scripts needed to run various tasks. To map a network drive, use the Tools menu of the Windows Explorer.

>
>
In order to be able to access the AFS volumes, you have to setup your OpenAFS token (Start->All Programs->OpenAFS->Client->authentication)
 

Available Commands at the DOS Prompt

(Hint: If you want to have a unix shell style "tab" behaviour to autocomplete a filename/directory in DOS, set the value "9" in the registry key: HKEY_CURRENT_USER\Software\Microsoft\Command Processor\CompletionChar)

Deleted:
<
<
When you open a new DOS window, you should execute a script equivalent to the group login on Linux, to set up all other environment variables necessary to work with CVS and CMT. Depending on whether or not you have installed the software locally, you should type:

  • %MYSITEROOT%\scripts\localsetup.bat (local installation)
  • S:\lhcb\scripts\lhcbsetup (AFS+DFS installation)

(Hint: If you have a desktop shortcut to start a DOS window, you can modify its properties to execute the script automatically: right-click on the icon, select Properties, Shortcut tab. In "Target:" append the string: /K S:\lhcb\scripts\lhcbsetup. In "Start in:" you could choose to start in %User_release_area%.)

  The following commands are available at the DOS prompt:
Changed:
<
<
  • getpack Similar behaviour than the Linux one with the same arguments. It does the checkout from the cvs repository and configures the package.
  • setenvProject Setup your environment for a particular project (e.g. setenvProject Brunel v31r7). Wildcard usage does not always work - you may need to specify the version you want at the command line.
  • cmt All cmt commands are available. This include the cmt broadcast, cmt checkout, etc.
  • make Is equivalent to "nmake /f nmake"
  • setup To execute the setup.bat in each package to set the necessary environment variables.
  • cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain).
  • doxygen Wrapper for the doxygen documentation tool. See here for details
  • set Standard DOS command to set environment variables. Useful for setting variables for the current DOS window only. e.g. set User_release_area=C:\cmtuser
>
>
  • getpack Similar behaviour than the Linux one with the same arguments. It does the checkout from the cvs repository and configures the package.
  • setenvProject Setup your environment for a particular project (e.g. setenvProject Brunel v31r7). Wildcard usage does not always work - you may need to specify the version you want at the command line.
  • cmt All cmt commands are available. This include the cmt broadcast, cmt checkout, etc.
  • make Is equivalent to "nmake /f nmake"
  • setup To execute the setup.bat in each package to set the necessary environment variables.
  • cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain).
  • doxygen Wrapper for the doxygen documentation tool. See here for details
  • set Standard DOS command to set environment variables. Useful for setting variables for the current DOS window only. e.g. set User_release_area=C:\cmtuser
 
Changed:
<
<
Building LHCb Software on Windows in Command Line Mode
>
>

Building LHCb Software on Windows in Command Line Mode

  Building software in Windows in command-line mode is not much different from building it in Linux. All the basic commands (cmt, cvs, etc.) should just work the same way in this environment. This is perhaps the easiest way to check that your package can be built and run in Windows if you are not used to the graphical integrated development environments (Visual Studio).

The following command sequence should just do the work of building and running (e.g. using Brunel)

Changed:
<
<
> BrunelEnv v24r2 > getpack Rec/Brunel v24r2 > cd Rec\Brunel\v24r2\cmt
>
>
> setenvProject Brunel v32r2 > getpack Rec/Brunel v32r2 > cd Rec\Brunel\v32r2\cmt
  > make (or "cmt broadcast make" for multiple packages)
Changed:
<
<
> setup > ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts
>
>
> cmt run ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts
 

Using Visual Studio .NET

Line: 164 to 155
  Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:
Changed:
<
<
> cd C:\cmtuser\Rec\Brunel\v24r2\cmt
>
>
> cd C:\cmtuser\Brunel_v32r2\Rec\Brunel\v32r2\cmt
  > setup > cmt build vsnet > ..\Visual\Brunel.sln
Line: 173 to 164
 The last command starts Visual Studio.NET. Before running e.g. Brunel, you may have to tell Visual Studio.NET about the job options file that you want to read:

  • In Solution Explorer select Brunel
Changed:
<
<
  • In Project Menu: "Set as StartUp Project"
>
>
  • In Project Menu: "Set as StartUp Project"
 
  • In Project Menu -> Properties...
    • Select Debugging the left hand panel
Changed:
<
<
    • In Command Arguments add: ..\options\v200402.opts
>
>
    • In Command Arguments add: ..\options\v200601.opts
  N.B. This step is only necessary once, it is remembered in subsequent Visual Studio.NET sessions with this executable

You are now ready to debug your program. Use [F5] to run the program in debug mode.

Changed:
<
<
Data Access on Windows

If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here.

>
>

Data Access on Windows

In principle, if you have installed the Castor client, you should be able to access Castor data files directly from Gaudi, as on Linux. This is however slow because it uses the public Castor 1 disk pool as opposed to the LHCb Castor 2 disk pool, so usually means a tape mount. For this reason, it is suggested that you make a disk copy of frequently used files.
 

Installed development tools on the Terminal Server

Line: 194 to 183
 
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
Changed:
<
<
-- HubertDegaudenzi - 30 Nov 2007
>
>
-- HubertDegaudenzi - 30 Nov 2007, MarcoCattaneo - 19 Dec 2007

Revision 132007-12-19 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 6 to 6
  In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris. The lhcbts installation is maintained by Hubert.
Changed:
<
<
>
>
 
Changed:
<
<

Preparing a standalone machine

>
>

Prerequisites

Preparing a standalone machine

  This section describes the software that has to be installed and configured on a standalone Windows machine. The instructions are given for machines in the CERN NICE environment. You can skip to the next section if you are using the Terminal Server, or if your PC was installed by the LHCb support team at CERN.
Changed:
<
<

Mandatory installations

>
>
Mandatory installations
 
  • Install the SSH application PuTTy
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
Changed:
<
<
    • In Start->Control Panel->System->Advanced Menu, define the environment variable CVS_RSH. It must be set to the location of the PuTTy application plink. Normally this will be C:\Program Files\PuTTY\plink.exe.
>
>
    • In Start->Control Panel->System->Advanced Menu, define the environment variable CVS_RSH. It must be set to the location of the PuTTy application plink. Normally this will be C:\Program Files\PuTTY\plink.exe.
 
  • Install Microsoft Visual Studio .NET
    • On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005)
    • Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1
Line: 25 to 26
 
    • On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC.
    • Otherwise you can try to download from here.
Changed:
<
<

Optional installations

>
>
Optional installations
 
  • OpenAFS
    • AFS is needed if you wish to access the centrally maintained LHCb software release area in AFS. In most cases it is more efficient to install the LHCb software stack locally (recommended).
    • If you choose to use AFS, installation instructions can be found here.
Line: 37 to 38
 
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.

Changed:
<
<

Preparing access to the Windows Terminal Server

>
>

Preparing access to the Windows Terminal Server

 This section describes the steps needed to access the LHCb Windows Terminal server for the first time. You can skip to the next section if you are using a standalone PC.

  • Install the appropriate remote desktop software if needed
Line: 59 to 60
 
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.

Changed:
<
<

Completing the installation

This section describes actions needed by all users both on standalone PCs and the Terminal Server
>
>

Completing the installation

This section describes actions needed by all users both on standalone PCs and the Terminal Server. To set environment variables, use Start->Control Panel->System->Advanced Menu
 
Added:
>
>
  • Define a User_release_area
    • The User_release_area environment variable must be defined to point to a read/write directory. This will be your working directory and, for speed of access reasons, it is recommended to set it up on a local disk (though remember that it is then up to you to back it up)
      • On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it
      • On the terminal server, User_release_area is predefined to point to E:\users\(username)\cmtuser
      • It is also possible to define the User_release_area to be your AFS cmtuser directory. Set it to Z:\cern.ch\user\(u)\(username)\cmtuser
  • If necessary, define GETPACK_USER
    • The GETPACK_USER environment variable must be defined if your Windows username is different from your lxplus username. Set it to the lxplus username that you use to when working on LHCb.
 
  • Configure SSH access to the CVS repository
    • Detailed instructions can be found here.
    • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
Line: 73 to 81
 
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
       
where (username) is the lxplus account you have used to set up your ssh key.
Deleted:
<
<
  • If your NICE username is different from the lxplus account that you are using, in Start->Control Panel->System->Advanced Menu set the GETPACK_USER global environment variable to your lxplus username.
 
  • If you wish to use emacs:
Changed:
<
<
    • Define the following environment variables (in Start->Control Panel->System->Advanced Menu)
>
>
    • Define the following environment variables
 
      • HOME
        • Points to your "home" area (e.g. C:\Users\<username> on the TS). Used by emacs as the location to look for a ".emacs" file.
      • EMACSDIR
        • The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro" * Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
Changed:
<
<

LHCb software usage

The LHCb software is located in a cascade of distinct release areas. These normally consist of a read/write User_release_area, and one or more read only areas where the official releases are installed. Every release of the LHCb software stack is installed in AFS, and also one the local disk of the LHCb Terminal Server. Normally it is more efficient to use the local installation
>
>

Opening terminal windows

By analogy with working on Linux, commands to check out, build and run the LHCb software are executed in a DOS terminal window, in which the LHCb environment has been set (via execution of a "login" script).
 
Changed:
<
<

User_release_area

The User_release_area environment variable must be defined (in Start->Control Panel->System->Advanced Menu) to point to a read/write directory. This will be your working directory and, for spped of access reasons, it is recommended to set it up on your local disk (though remember that it is then up to you to back it up) * On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it * On the terminal server, User_release_area is predefined to point to E:\users\(username)\cmtuser * It is also possible to define the User_release_area to be your AFS cmtuser directory. Set it to Z:\cern.ch\user\(u)\(username)\cmtuser
>
>

Pre-defined terminal windows on the LHCb terminal server

When you log in to the LHCb terminal server, you will find two terminal icons. These shortcuts provide a shell with the CMT environment set up for usage of either the local LHCb software installation on the machine ("LHCb local" icon) or the AFS software installation ("LHCb AFS" icon)

Setting up a terminal window on a standalone machine

LHCb software installations

The LHCb software is located in a cascade of distinct release areas. These normally consist of a read/write User_release_area, and one or more read only areas where the official releases are installed. Every release of the LHCb software stack is installed in AFS, and also one the local disk of the LHCb Terminal Server. Normally it is more efficient to use the local installation
 

Using locally installed releases

These instructions should be followed if you have chosen to use the local installation of the LHCb software stack (recommended)

Revision 122007-12-19 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 10 to 10
 

Preparing a standalone machine

Changed:
<
<
This section describes the software that has to be installed and configured on a standalone Windows machine. The instructions are given for machines in the CERN NICE environment. You can skip to the next section if you are using the Terminal Server, or if your PC was installed by the LHCb support team at CERN.
>
>
This section describes the software that has to be installed and configured on a standalone Windows machine. The instructions are given for machines in the CERN NICE environment. You can skip to the next section if you are using the Terminal Server, or if your PC was installed by the LHCb support team at CERN.
 

Mandatory installations

Line: 26 to 26
 
    • Otherwise you can try to download from here.

Optional installations

Changed:
<
<
  • Install OpenAFS
>
>
  • OpenAFS
 
    • AFS is needed if you wish to access the centrally maintained LHCb software release area in AFS. In most cases it is more efficient to install the LHCb software stack locally (recommended).
    • If you choose to use AFS, installation instructions can be found here.
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
    • In Start->Control Panel->System->Advanced Menu, define the environment variable AFSROOT. It should be set to Z:
Changed:
<
<
  • Install Emacs (optional)
>
>
  • Emacs
 
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.

Changed:
<
<
>
>
 

Preparing access to the Windows Terminal Server

Changed:
<
<
This section describes the steps needed to access the LHCb Windows Terminal server for the first time. You can skip to the next section if you are using a standalone PC.
>
>
This section describes the steps needed to access the LHCb Windows Terminal server for the first time. You can skip to the next section if you are using a standalone PC.
 
  • Install the appropriate remote desktop software if needed
    • Installation instructions can be found from here for Windows, Mac and linux users.
Line: 58 to 58
 
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
Added:
>
>
 

Completing the installation

This section describes actions needed by all users both on standalone PCs and the Terminal Server
Line: 69 to 70
 
      • Where <path-to-private-key> is the complete path to your private ssh key.
      • Double clicking this new icon will start up pagent and add you key.
    • If the SSH configuration was successful, you should be able to connect without password with only the private/public key verification. In order to check this, you can try:
Changed:
<
<

>
>
 C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
Changed:
<
<
where (username) is the lxplus account you have used to set up your ssh key.
>
>
where (username) is the lxplus account you have used to set up your ssh key.
 
  • If your NICE username is different from the lxplus account that you are using, in Start->Control Panel->System->Advanced Menu set the GETPACK_USER global environment variable to your lxplus username.
  • If you wish to use emacs:
    • Define the following environment variables (in Start->Control Panel->System->Advanced Menu)
      • HOME
Changed:
<
<
        • Points to your "home" area (e.g. C:\Users\ on the TS). Used by emacs as the location to look for a ".emacs" file.
>
>
        • Points to your "home" area (e.g. C:\Users\<username> on the TS). Used by emacs as the location to look for a ".emacs" file.
 
      • EMACSDIR
        • The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro" * Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)

Revision 112007-12-18 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 8 to 8
 
Changed:
<
<

Prerequisites

>
>

Preparing a standalone machine

 
Changed:
<
<
Before you can use the LHCb software, you will need to do a few tasks. These tasks differ slightly depending on where you wish to run the software; Either on a standalone CERN NICE PC, or using the Windows Terminal Server.
>
>
This section describes the software that has to be installed and configured on a standalone Windows machine. The instructions are given for machines in the CERN NICE environment. You can skip to the next section if you are using the Terminal Server, or if your PC was installed by the LHCb support team at CERN.
 
Changed:
<
<

For Standalone Machines

N.B. If your PC was installed by the LHCb support team at CERN, it should already have been configured according to the following instructions, including AFS. N.B. If you previously had a Visual Studio 6 installation, remove it

You will need to set up on your PC the following software :-

>
>

Mandatory installations

 
  • Install the SSH application PuTTy
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
Added:
>
>
    • In Start->Control Panel->System->Advanced Menu, define the environment variable CVS_RSH. It must be set to the location of the PuTTy application plink. Normally this will be C:\Program Files\PuTTY\plink.exe.
 
  • Install Microsoft Visual Studio .NET
    • On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005)
    • Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1
Line: 28 to 24
 
    • Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows.
    • On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC.
    • Otherwise you can try to download from here.
Changed:
<
<
  • Install OpenAFS (optional)
    • You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS.
>
>

Optional installations

  • Install OpenAFS
    • AFS is needed if you wish to access the centrally maintained LHCb software release area in AFS. In most cases it is more efficient to install the LHCb software stack locally (recommended).
 
    • If you choose to use AFS, installation instructions can be found here.
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
Added:
>
>
    • In Start->Control Panel->System->Advanced Menu, define the environment variable AFSROOT. It should be set to Z:
 
  • Install Emacs (optional)
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.

Changed:
<
<

For the Windows Terminal Server

>
>

Preparing access to the Windows Terminal Server

This section describes the steps needed to access the LHCb Windows Terminal server for the first time. You can skip to the next section if you are using a standalone PC.
 
Changed:
<
<
  • Install the appropriate remote desktop software
    • Installation instructions can be found from here for Windows, Mac and linux users.
      • Note - rdesktop has already been installed on lxplus.
>
>
  • Install the appropriate remote desktop software if needed
    • Installation instructions can be found from here for Windows, Mac and linux users.
      • Note - rdesktop has already been installed in the Scientific Linux CERN distribution.
 
  • Register your CERN NICE account for TS access
Changed:
<
<
    • This can also be done from here, by following the registration link.
>
>
    • This can also be done from here.
 
  • Start a session on the terminal server lhcbts.cern.ch.
    • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Line: 58 to 58
 
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
Changed:
<
<

For both standalone and TS sessions

>
>

Completing the installation

This section describes actions needed by all users both on standalone PCs and the Terminal Server
 
Deleted:
<
<
Once you performed the prerequisites as above:

 
  • Configure SSH access to the CVS repository
    • Detailed instructions can be found here.
    • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
Line: 70 to 68
 
      • Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key>
      • Where <path-to-private-key> is the complete path to your private ssh key.
    • Double clicking this new icon will start up pagent and add you key.
Changed:
<
<
  • Create a .emacs file in your HOME area (optional)
    • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
    • If you don't have the variable HOME defined, follow the instructions here to define it.
      • NOTE For Terminal Server users : Emacs is already installed and available from the start Menu.

Define Environment Variables

The following environment variables are mandatory and must be defined (in Start->Control Panel->System->Advanced Menu)

  • TEMP
    • CMT needs to write some temporary files: it writes on %TEMP%.
    • You should make sure that the TEMP environment variable points to an area with write access.
  • User_release_area *The first location where CMT is looking for projects. You should create a directory, typically on the local disk ( e.g. C:\cmtuser), and set User_release_area to point to it.
    • NOTE For Terminal Server users : For local files, we recommend using the directory C:/Users//cmtuser
  • CVS_RSH * Must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink.exe".

The following variable is optional, it should only be set if you want CMT to access the AFS software release areas

  • AFSROOT
    • Set the environment variable AFSROOT to Z:

The following variables are optional, they are needed if you want to use emacs as editor

>
>
    • If the SSH configuration was successful, you should be able to connect without password with only the private/public key verification. In order to check this, you can try:
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
where (username) is the lxplus account you have used to set up your ssh key.
  • If your NICE username is different from the lxplus account that you are using, in Start->Control Panel->System->Advanced Menu set the GETPACK_USER global environment variable to your lxplus username.
  • If you wish to use emacs:
    • Define the following environment variables (in Start->Control Panel->System->Advanced Menu)
 
  • HOME
    • Points to your "home" area (e.g. C:\Users\ on the TS). Used by emacs as the location to look for a ".emacs" file.
  • EMACSDIR
    • The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro"
Added:
>
>
* Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
 
Changed:
<
<

Install a software release (optional)

>
>

LHCb software usage

The LHCb software is located in a cascade of distinct release areas. These normally consist of a read/write User_release_area, and one or more read only areas where the official releases are installed. Every release of the LHCb software stack is installed in AFS, and also one the local disk of the LHCb Terminal Server. Normally it is more efficient to use the local installation
 
Changed:
<
<
If you have chosen to not use AFS, you have to install at least one version of the LHCb software stack, using the installProject.py script.
>
>

User_release_area

The User_release_area environment variable must be defined (in Start->Control Panel->System->Advanced Menu) to point to a read/write directory. This will be your working directory and, for spped of access reasons, it is recommended to set it up on your local disk (though remember that it is then up to you to back it up) * On a standalone PC, create a directory C:\cmtuser and set User_release_area to point to it * On the terminal server, User_release_area is predefined to point to E:\users\(username)\cmtuser * It is also possible to define the User_release_area to be your AFS cmtuser directory. Set it to Z:\cern.ch\user\(u)\(username)\cmtuser
 
Added:
>
>

Using locally installed releases

These instructions should be followed if you have chosen to use the local installation of the LHCb software stack (recommended)

  • On the terminal server, one of the icons on the desktop is called "LHCb Local". This shortcut provides a shell with your CMT environment set up for the usage of the local software installed on the machine (E:\soft). This software location has been installed with the install_project.py scripts and should contain the latest software releases of the LHCb projects

  • On a standalone PC, you have to install yourself at least one version of the LHCb software stack, using the installProject.py script.
 
  • Create a directory on the local disk under which you will install the software. e.g. C:\releases
  • Define the environment variable MYSITEROOT to point to the above directory
Changed:
<
<
  • Import the software by following the instructions given here.
>
>
    • Import the software by following the instructions given here.

Using the AFS release area

These instructions should be followed if you have chosen to use the AFS installation of the LHCb software stack. This method is slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally

As usual, in order to be able to access the AFS volumes, you have to setup your OpenAFS token (Start->All Programs->OpenAFS->Client->authentication).

  • On the terminal server, there is an icon on the desktop is called "LHCb AFS". This shortcut provides a shell with your CMT environment set up for the usage of the AFS software.
 

Map Network Drives (optional)

Line: 178 to 176
  If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here.
Deleted:
<
<

LHCbTS windows 2003 server

The lhcbts.cern.ch machine is a virtual windows 2003 server dedicated to LHCb. Provided that you are registred as a CERN Terminal Server user, you can access the server with the usual command:

 pcdn ~ > rdesktop -d CERN -g 1024x768 -T "LHCb TS" lhcbts.cern.ch

Environment

A few environment variables are already defined globally on the lhcbts machine like AFS ("Z:"), AFSROOT ("Z:"), CVS_RSH ("C:\Program Files\PuTTy\plink.exe"). However you have still to set up your CVS and AFS access.

CVS access

You have to configure your ssh key pair as described above. For the usage of the getpack utility, it is important to be able to connect without password with only the private/public key verification. In order to check this, you can try:

C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
Where (username) is the lxplus account you have used to set up your ssh key.

The second thing to do is to instruct the getpack utility which lxplus account you are using (it is only needed if this name is different from your NICE account name). This is achieved by setting the global environment variable GETPACK_USER in Start->Control Panel->System->Advanced Menu.

AFS access

As usual, in order to be able to access the AFS volumes, you have to setup your OpenAFS token (Start->All Programs->OpenAFS->Client->authentication).

Local LHCb software usage

One of the icons on the desktop is called "LHCb Local". This shortcut provide a shell with your CMT environment set up for the usage of the local software installed on the machine (E:\soft). This software location has been installed with the install_project.py scripts and should contain the latest software releases of the LHCb projects.

By default, the starting directory is on the local disk at E:\users\(username)\cmtuser. The instructions to configure it to point elsewhere are here

AFS LHCB software usage

One other icon on the desktop is called "LHCb AFS". This shortcut provide a shell with your CMT environment set up for the usage of the AFS software. This method is slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally.

By default, the starting directory is on the local disk at E:\users\(username)\cmtuser. The instructions to configure it to point elsewhere are here

Defining your user release area

For both AFS and Local LHCb software usage, you can define your user release area. By default this point in the E:\users directory but can be defined to be something else like User_release_area=Z:\cern.ch\user\(u)\(username)\cmtuser. This is achieved by defining a global environment variable for your account on this machine (Start->Control Panel->System->Advanced Menu) .

The 2 previous icons will take this into account.

 
Changed:
<
<

Installed development tools

>
>

Installed development tools on the Terminal Server

  Beside the Windows Visual C++ development tools, a bunch of other development tools have also been installed on LHCbTS:
Some editors
Vim, Emacs, XEmacs

Revision 102007-12-18 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Changed:
<
<
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the CERN development Terminal Server. In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris.
>
>
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the LHCb Windows Terminal Server at CERN (lhcbts.cern.ch). The Terminal Server is a virtual Windows 2003 server which allows concurrent connections.
 
Changed:
<
<
There is now a new machine dedicated to LHCb called lhcbts.cern.ch. This is a virtual Windows 2003 server which allows concurrent connections and you can find specific instructions for its usage at the end of this page.
>
>
In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris. The lhcbts installation is maintained by Hubert.
 

Prerequisites

Changed:
<
<
Before you can use the LHCb software, you will need to do a few tasks. These tasks differ slightly depending on where you wish to run the software; Either on a standalone CERN NICE PC, or using the CERN windows terminal server.
>
>
Before you can use the LHCb software, you will need to do a few tasks. These tasks differ slightly depending on where you wish to run the software; Either on a standalone CERN NICE PC, or using the Windows Terminal Server.
 

For Standalone Machines

N.B. If your PC was installed by the LHCb support team at CERN, it should already have been configured according to the following instructions, including AFS.

Changed:
<
<
N.B. If you previously had a Visual Studio 6 installation, remove it
>
>
N.B. If you previously had a Visual Studio 6 installation, remove it
  You will need to set up on your PC the following software :-
Line: 31 to 31
 
  • Install OpenAFS (optional)
    • You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS.
    • If you choose to use AFS, installation instructions can be found here.
Added:
>
>
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
 
  • Install Emacs (optional)
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.

Changed:
<
<

For the CERN Terminal Server

>
>

For the Windows Terminal Server

 
  • Install the appropriate remote desktop software
    • Installation instructions can be found from here for Windows, Mac and linux users.
      • Note - rdesktop has already been installed on lxplus.
  • Register your CERN NICE account for TS access
    • This can also be done from here, by following the registration link.
Changed:
<
<
  • Start a session on the terminal server cerntsdev01.cern.ch.
>
>
  • Start a session on the terminal server lhcbts.cern.ch.
 
    • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is
       pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" lhcbts.cern.ch
Line: 71 to 74
 
    • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
    • If you don't have the variable HOME defined, follow the instructions here to define it.
      • NOTE For Terminal Server users : Emacs is already installed and available from the start Menu.
Deleted:
<
<
  • If you want to access the AFS software release areas, configure AFS
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
 

Define Environment Variables

Line: 87 to 86
 
  • User_release_area *The first location where CMT is looking for projects. You should create a directory, typically on the local disk ( e.g. C:\cmtuser), and set User_release_area to point to it.
    • NOTE For Terminal Server users : For local files, we recommend using the directory C:/Users//cmtuser
Deleted:
<
<
  • CVSROOT
    • Must be set to ":ext:isscvs.cern.ch:/local/reps/lhcb" to enable ssh access to the server.
 
  • CVS_RSH
Changed:
<
<
* Must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".
>
>
* Must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink.exe".
  The following variable is optional, it should only be set if you want CMT to access the AFS software release areas
Line: 197 to 194
 

CVS access

Changed:
<
<
You have to configure your ssh key pair as it is describe above. For the usage of the getpack utility, it is important to be able to connect without password with only the private/public key verification. In order to check this, you can try:
>
>
You have to configure your ssh key pair as described above. For the usage of the getpack utility, it is important to be able to connect without password with only the private/public key verification. In order to check this, you can try:
 
C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
Where (username) is the lxplus account you have used to set up your ssh key.
Changed:
<
<
The second thing to do is to instruct the getpack utility which lxplus account you are using (it is only needed if this name is different from your nice account name). This is achieved by setting the global environment variable GETPACK_USER in Start->Control Panel->System->Advanced Menu.
>
>
The second thing to do is to instruct the getpack utility which lxplus account you are using (it is only needed if this name is different from your NICE account name). This is achieved by setting the global environment variable GETPACK_USER in Start->Control Panel->System->Advanced Menu.
 

AFS access

Revision 92007-12-05 - ChristopherRJones

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 45 to 45
 
  • Start a session on the terminal server cerntsdev01.cern.ch.
    • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Changed:
<
<
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch
>
>
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" lhcbts.cern.ch
 
  • Connection Problems ?
    • If you experience problems connecting to the Terminal Server from outside CERN, it is possible that your local network is blocking connections through the RDP port 3389. Symptoms are, for example with rdesktop :-

Changed:
<
<
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch
>
>
pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" lhcbts.cern.ch
 pcdn ~ > ERROR: connect: Connection refused
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.

Revision 82007-12-04 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Changed:
<
<
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the CERN development Terminal Server. In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris.
>
>
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the CERN development Terminal Server. In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris.
  There is now a new machine dedicated to LHCb called lhcbts.cern.ch. This is a virtual Windows 2003 server which allows concurrent connections and you can find specific instructions for its usage at the end of this page.
Line: 20 to 20
 You will need to set up on your PC the following software :-

  • Install the SSH application PuTTy
Changed:
<
<
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
>
>
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
 
  • Install Microsoft Visual Studio .NET
    • On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005)
    • Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1
  • Install the CERN Castor software
    • Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows.
    • On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC.
Changed:
<
<
    • Otherwise you can try to download from here.
>
>
    • Otherwise you can try to download from here.
 
  • Install OpenAFS (optional)
    • You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS.
Changed:
<
<
    • If you choose to use AFS, installation instructions can be found here.
>
>
    • If you choose to use AFS, installation instructions can be found here.
 
  • Install Emacs (optional)
Changed:
<
<
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.
>
>
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.
 

For the CERN Terminal Server

  • Install the appropriate remote desktop software
Changed:
<
<
    • Installation instructions can be found from here for Windows, Mac and linux users.
>
>
    • Installation instructions can be found from here for Windows, Mac and linux users.
 
      • Note - rdesktop has already been installed on lxplus.
  • Register your CERN NICE account for TS access
Changed:
<
<
    • This can also be done from here, by following the registration link.
>
>
    • This can also be done from here, by following the registration link.
 
  • Start a session on the terminal server cerntsdev01.cern.ch.
    • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

Line: 53 to 53
 pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch pcdn ~ > ERROR: connect: Connection refused
Changed:
<
<
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
>
>
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
 

For both standalone and TS sessions

Once you performed the prerequisites as above:

Added:
>
>
 
  • Configure SSH access to the CVS repository
Changed:
<
<
    • Detailed instructions can be found here.
>
>
    • Detailed instructions can be found here.
 
    • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
      • Create a new shortcut on your desktop (right click on the desktop)
      • Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key>
      • Where <path-to-private-key> is the complete path to your private ssh key.
    • Double clicking this new icon will start up pagent and add you key.
  • Create a .emacs file in your HOME area (optional)
Changed:
<
<
    • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
    • If you don't have the variable HOME defined, follow the instructions here to define it.
>
>
    • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
    • If you don't have the variable HOME defined, follow the instructions here to define it.
 
      • NOTE For Terminal Server users : Emacs is already installed and available from the start Menu.
  • If you want to access the AFS software release areas, configure AFS
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
Added:
>
>
 

Define Environment Variables

The following environment variables are mandatory and must be defined (in Start->Control Panel->System->Advanced Menu)

Line: 108 to 110
 
  • Create a directory on the local disk under which you will install the software. e.g. C:\releases
  • Define the environment variable MYSITEROOT to point to the above directory
Changed:
<
<
  • Import the software by following the instructions given here.
>
>
  • Import the software by following the instructions given here.
 

Map Network Drives (optional)

Changed:
<
<
If you have chosen to use the AFS release area, and you are at CERN, we recommend that you map the directory \\cern.ch\dfs\Experiments to the S: drive. This directory contains a collection of scripts needed to run various tasks. To map a network drive, use the Tools menu of the Windows Explorer.
>
>
If you have chosen to use the AFS release area, and you are at CERN, we recommend that you map the directory \\cern.ch\dfs\Experiments to the S: drive. This directory contains a collection of scripts needed to run various tasks. To map a network drive, use the Tools menu of the Windows Explorer.
 

Available Commands at the DOS Prompt

Line: 133 to 135
 
  • cmt All cmt commands are available. This include the cmt broadcast, cmt checkout, etc.
  • make Is equivalent to "nmake /f nmake"
  • setup To execute the setup.bat in each package to set the necessary environment variables.
Changed:
<
<
  • cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain).
  • doxygen Wrapper for the doxygen documentation tool. See here for details
>
>
  • cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain).
  • doxygen Wrapper for the doxygen documentation tool. See here for details
 
  • set Standard DOS command to set environment variables. Useful for setting variables for the current DOS window only. e.g. set User_release_area=C:\cmtuser

Building LHCb Software on Windows in Command Line Mode

Line: 153 to 155
 

Using Visual Studio .NET

Changed:
<
<
Note to Terminal Server Users : In order to use the graphical interface to Visual Studio .Net you need special access rights. You should ask Joel to add you to the "Debugger Users" group on the terminal server.
>
>
Note to Terminal Server Users : In order to use the graphical interface to Visual Studio .Net you need special access rights. You should ask Joel to add you to the "Debugger Users" group on the terminal server.
  Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:
Line: 177 to 179
  Data Access on Windows
Changed:
<
<
If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here
>
>
If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here.
 
Added:
>
>
 

LHCbTS windows 2003 server

Added:
>
>
The lhcbts.cern.ch machine is a virtual windows 2003 server dedicated to LHCb. Provided that you are registred as a CERN Terminal Server user, you can access the server with the usual command:
 pcdn ~ > rdesktop -d CERN -g 1024x768 -T "LHCb TS" lhcbts.cern.ch
 

Environment

Changed:
<
<

CVS

>
>
A few environment variables are already defined globally on the lhcbts machine like AFS ("Z:"), AFSROOT ("Z:"), CVS_RSH ("C:\Program Files\PuTTy\plink.exe"). However you have still to set up your CVS and AFS access.

CVS access

You have to configure your ssh key pair as it is describe above. For the usage of the getpack utility, it is important to be able to connect without password with only the private/public key verification. In order to check this, you can try:

C:\> "C:\Program Files\PuTTY\plink.exe" (username)@isscvs.cern.ch
Where (username) is the lxplus account you have used to set up your ssh key.

The second thing to do is to instruct the getpack utility which lxplus account you are using (it is only needed if this name is different from your nice account name). This is achieved by setting the global environment variable GETPACK_USER in Start->Control Panel->System->Advanced Menu.

 

AFS access

Changed:
<
<

Local software usage

>
>
As usual, in order to be able to access the AFS volumes, you have to setup your OpenAFS token (Start->All Programs->OpenAFS->Client->authentication).

Local LHCb software usage

One of the icons on the desktop is called "LHCb Local". This shortcut provide a shell with your CMT environment set up for the usage of the local software installed on the machine (E:\soft). This software location has been installed with the install_project.py scripts and should contain the latest software releases of the LHCb projects.
 
Changed:
<
<

AFS software usage

>
>
By default, the starting directory is on the local disk at E:\users\(username)\cmtuser. The instructions to configure it to point elsewhere are here
 
Added:
>
>

AFS LHCB software usage

One other icon on the desktop is called "LHCb AFS". This shortcut provide a shell with your CMT environment set up for the usage of the AFS software. This method is slower but can be very handy if the working files are not in CVS (yet) or if the needed projects have not been installed locally.

By default, the starting directory is on the local disk at E:\users\(username)\cmtuser. The instructions to configure it to point elsewhere are here

 

Defining your user release area

Added:
>
>
For both AFS and Local LHCb software usage, you can define your user release area. By default this point in the E:\users directory but can be defined to be something else like User_release_area=Z:\cern.ch\user\(u)\(username)\cmtuser. This is achieved by defining a global environment variable for your account on this machine (Start->Control Panel->System->Advanced Menu) .

The 2 previous icons will take this into account.

 

Installed development tools

Revision 72007-12-04 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 15 to 15
 

For Standalone Machines

N.B. If your PC was installed by the LHCb support team at CERN, it should already have been configured according to the following instructions, including AFS.

Changed:
<
<
N.B. If you previously had a Visual Studio 6 installation, remove it
>
>
N.B. If you previously had a Visual Studio 6 installation, remove it
  You will need to set up on your PC the following software :-

Revision 62007-12-04 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Changed:
<
<
Before you can use the LHCb software, you will need to do a few tasks. These tasks differ slightly depending on where you wish to run the software; Either on a standalone CERN NICE PC, or using the CERN windows terminal server. There is now a new machine dedicated to LHCb called lhcbts.cern.ch. This is a virtual Windows 2003 server which allows concurrent connections.
>
>
These instructions aim to be a guide to setting up and running the LHCb software on a standalone windows machine, or using the CERN development Terminal Server. In case of installation problems, errors in the instructions or suggestions for improvements please contact Marco and Chris.

There is now a new machine dedicated to LHCb called lhcbts.cern.ch. This is a virtual Windows 2003 server which allows concurrent connections and you can find specific instructions for its usage at the end of this page.

 

Prerequisites

Added:
>
>
Before you can use the LHCb software, you will need to do a few tasks. These tasks differ slightly depending on where you wish to run the software; Either on a standalone CERN NICE PC, or using the CERN windows terminal server.
 

For Standalone Machines

N.B. If your PC was installed by the LHCb support team at CERN, it should already have been configured according to the following instructions, including AFS.

Line: 152 to 156
 Note to Terminal Server Users : In order to use the graphical interface to Visual Studio .Net you need special access rights. You should ask Joel to add you to the "Debugger Users" group on the terminal server.

Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:

Changed:
<
<
>
>
  > cd C:\cmtuser\Rec\Brunel\v24r2\cmt > setup > cmt build vsnet > ..\Visual\Brunel.sln
Added:
>
>
  The last command starts Visual Studio.NET. Before running e.g. Brunel, you may have to tell Visual Studio.NET about the job options file that you want to read:

* In Solution Explorer select Brunel * In Project Menu: "Set as StartUp Project" * In Project Menu -> Properties...

Changed:
<
<
o Select Debugging the left hand panel o In Command Arguments add: ..\options\v200402.opts
>
>
    • Select Debugging the left hand panel
    • In Command Arguments add: ..\options\v200402.opts
  N.B. This step is only necessary once, it is remembered in subsequent Visual Studio.NET sessions with this executable
Line: 174 to 179
  If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here
Changed:
<
<

LHCbTS environment

>
>

LHCbTS windows 2003 server

Environment

CVS

AFS access

 

Local software usage

Line: 184 to 195
 

Installed development tools

Added:
>
>
Beside the Windows Visual C++ development tools, a bunch of other development tools have also been installed on LHCbTS:
Some editors
Vim, Emacs, XEmacs
The Eclispe IDE 3.3 (Europa)
with support for Python and C++ development.
CVS tools
WinCVS, TortoiseCVS. To be noted that these tools will only work on windows with the "ext" method with CVS_RSH=ssh. The "kserver" (kerberos) method which is commonly used on lxplus (and on the AFS volumes) will not work. On windows by default, the getpack utility uses the ssh method for the CVS checkout. It is advised to setup your ssh key pair in order to be able to issue CVS commands without having to give the password each time.
 -- HubertDegaudenzi - 30 Nov 2007

Revision 52007-12-03 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 109 to 109
 

Map Network Drives (optional)

If you have chosen to use the AFS release area, and you are at CERN, we recommend that you map the directory \\cern.ch\dfs\Experiments to the S: drive. This directory contains a collection of scripts needed to run various tasks. To map a network drive, use the Tools menu of the Windows Explorer.

Changed:
<
<
Available Commands at the DOS Prompt
>
>

Available Commands at the DOS Prompt

  (Hint: If you want to have a unix shell style "tab" behaviour to autocomplete a filename/directory in DOS, set the value "9" in the registry key: HKEY_CURRENT_USER\Software\Microsoft\Command Processor\CompletionChar)
Line: 137 to 138
 Building software in Windows in command-line mode is not much different from building it in Linux. All the basic commands (cmt, cvs, etc.) should just work the same way in this environment. This is perhaps the easiest way to check that your package can be built and run in Windows if you are not used to the graphical integrated development environments (Visual Studio).

The following command sequence should just do the work of building and running (e.g. using Brunel)

Added:
>
>
  > BrunelEnv v24r2 > getpack Rec/Brunel v24r2 > cd Rec\Brunel\v24r2\cmt > make (or "cmt broadcast make" for multiple packages) > setup > ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts
Added:
>
>
 

Using Visual Studio .NET

Revision 42007-12-03 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 76 to 76
 The following environment variables are mandatory and must be defined (in Start->Control Panel->System->Advanced Menu)

* TEMP

Changed:
<
<
o CMT needs to write some temporary files: it writes on %TEMP%. o You should make sure that the TEMP environment variable points to an area with write access.
>
>
    • CMT needs to write some temporary files: it writes on %TEMP%.
    • You should make sure that the TEMP environment variable points to an area with write access.
  * User_release_area
Changed:
<
<
o The first location where CMT is looking for projects. You should create a directory, typically on the local disk ( e.g. C:\cmtuser), and set User_release_area to point to it. o NOTE For Terminal Server users : For local files, we recommend using the directory C:/Users//cmtuser
>
>
*The first location where CMT is looking for projects. You should create a directory, typically on the local disk ( e.g. C:\cmtuser), and set User_release_area to point to it.
    • NOTE For Terminal Server users : For local files, we recommend using the directory C:/Users//cmtuser
  * CVSROOT
Changed:
<
<
o Must be set to ":ext:isscvs.cern.ch:/local/reps/lhcb" to enable ssh access to the server.
>
>
    • Must be set to ":ext:isscvs.cern.ch:/local/reps/lhcb" to enable ssh access to the server.
  * CVS_RSH
Changed:
<
<
o Must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".
>
>
* Must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".
  The following variable is optional, it should only be set if you want CMT to access the AFS software release areas

* AFSROOT

Changed:
<
<
o Set the environment variable AFSROOT to Z:
>
>
    • Set the environment variable AFSROOT to Z:
  The following variables are optional, they are needed if you want to use emacs as editor

* HOME

Changed:
<
<
o Points to your "home" area (e.g. C:\Users\ on the TS). Used by emacs as the location to look for a ".emacs" file.
>
>
    • Points to your "home" area (e.g. C:\Users\ on the TS). Used by emacs as the location to look for a ".emacs" file.
  * EMACSDIR
Changed:
<
<
o The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro"
>
>
    • The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro"
 

Install a software release (optional)

Revision 32007-12-03 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 15 to 15
  You will need to set up on your PC the following software :-
Changed:
<
<
  • Install the SSH application PuTTy
>
>
  • Install the SSH application PuTTy
 
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
  • Install Microsoft Visual Studio .NET
    • On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005)
Line: 24 to 24
 
    • Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows.
    • On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC.
    • Otherwise you can try to download from here.
Changed:
<
<
>
>
  • Install OpenAFS (optional)
 
    • You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS.
    • If you choose to use AFS, installation instructions can be found here.
  • Install Emacs (optional)
Line: 51 to 51
 
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
Changed:
<
<
For both standalone and TS sessions, once you performed the prerequisites as above :-
>
>

For both standalone and TS sessions

 
Changed:
<
<
* Configure SSH access to the CVS repository o Detailed instructions can be found here. o NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :- + Create a new shortcut on your desktop (right click on the desktop) + Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key> + Where <path-to-private-key> is the complete path to your private ssh key. o Double clicking this new icon will start up pagent and add you key.
>
>
Once you performed the prerequisites as above:
 
Added:
>
>
  • Configure SSH access to the CVS repository
    • Detailed instructions can be found here.
    • NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :
      • Create a new shortcut on your desktop (right click on the desktop)
      • Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key>
      • Where <path-to-private-key> is the complete path to your private ssh key.
    • Double clicking this new icon will start up pagent and add you key.
  * Create a .emacs file in your HOME area (optional)
Changed:
<
<
o Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !) + If you don't have the variable HOME defined, follow the instructions here to define it. + NOTE For Terminal Server users : Emacs is already installed and available from the start Menu.
>
>
    • Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !)
    • If you don't have the variable HOME defined, follow the instructions here to define it.
      • NOTE For Terminal Server users : Emacs is already installed and available from the start Menu.
  * If you want to access the AFS software release areas, configure AFS
Changed:
<
<
o Using the AFS application (a little padlock in the system tray) :- + Mandatory : Mount /afs as Z: + Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
>
>
    • Using the AFS application (a little padlock in the system tray) :-
      • Mandatory : Mount /afs as Z:
      • Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:
 

Define Environment Variables

Revision 22007-11-30 - HubertDegaudenzi

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Windows development environment

Line: 16 to 16
  You will need to set up on your PC the following software :-

* Install the SSH application PuTTy

Changed:
<
<
o If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
>
>
    • If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.
  * Install Microsoft Visual Studio .NET
Changed:
<
<
o On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005) o Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1
>
>
    • On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005)
    • Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1
  * Install the CERN Castor software
Changed:
<
<
o Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows. o On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC. o Otherwise you can try to download from here.
>
>
    • Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows.
    • On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC.
    • Otherwise you can try to download from here.
  * Install OpenAFS (optional)
Changed:
<
<
o You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS. o If you choose to use AFS, installation instructions can be found here.
>
>
    • You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS.
    • If you choose to use AFS, installation instructions can be found here.
  * Install Emacs (optional)
Changed:
<
<
o If you are familiar with emacs and wish to use this on windows, follow the instructions here.
>
>
    • If you are familiar with emacs and wish to use this on windows, follow the instructions here.
 
Changed:
<
<
For the CERN Terminal Server
>
>

For the CERN Terminal Server

  * Install the appropriate remote desktop software
Changed:
<
<
o Installation instructions can be found from here for Windows, Mac and linux users. + Note - rdesktop has already been installed on lxplus.
>
>
    • Installation instructions can be found from here for Windows, Mac and linux users.
      • Note - rdesktop has already been installed on lxplus.
  * Register your CERN NICE account for TS access
Changed:
<
<
o This can also be done from here, by following the registration link.
>
>
    • This can also be done from here, by following the registration link.
  * Start a session on the terminal server cerntsdev01.cern.ch.
Changed:
<
<
o For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is
>
>
    • For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

  pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch
Changed:
<
<
>
>
  * Connection Problems ?
Changed:
<
<
o If you experience problems connecting to the Terminal Server from outside CERN, it is possible that your local network is blocking connections through the RDP port 3389. Symptoms are, for example with rdesktop :-
>
>
    • If you experience problems connecting to the Terminal Server from outside CERN, it is possible that your local network is blocking connections through the RDP port 3389. Symptoms are, for example with rdesktop :-

  pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch pcdn ~ > ERROR: connect: Connection refused
Changed:
<
<
o If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
>
>
    • If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.
  For both standalone and TS sessions, once you performed the prerequisites as above :-
Line: 178 to 173
  If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here
Changed:
<
<

LHCbTS environment

>
>

LHCbTS environment

 

Local software usage

Revision 12007-11-30 - HubertDegaudenzi

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbComputing"

Windows development environment

Before you can use the LHCb software, you will need to do a few tasks. These tasks differ slightly depending on where you wish to run the software; Either on a standalone CERN NICE PC, or using the CERN windows terminal server. There is now a new machine dedicated to LHCb called lhcbts.cern.ch. This is a virtual Windows 2003 server which allows concurrent connections.

Prerequisites

For Standalone Machines

N.B. If your PC was installed by the LHCb support team at CERN, it should already have been configured according to the following instructions, including AFS. N.B. If you previously had a Visual Studio 6 installation, remove it

You will need to set up on your PC the following software :-

* Install the SSH application PuTTy o If you are on CERN-NICE, you can install using the "Add/Remove CMF packages" facility on your PC. Otherwise you can download the latest version from here.

* Install Microsoft Visual Studio .NET o On CERN-NICE, use the "Add/Remove CMF packages" facility on your PC to add Microsoft Visual Studio.NET 2003 (not 2005) o Follow the instructions in the setup wizard. Most defaults are sensible, but you may want to skip installation of Web server extensions in step 1

* Install the CERN Castor software o Provides various useful commands, such as rfcp. Note that Castor 2 is not (yet) available for Windows. o On CERN-NICE, install using the "Add/Remove CMF packages" facility on your PC. o Otherwise you can try to download from here.

* Install OpenAFS (optional) o You can choose whether to install all the LHCb software stack locally (recommended) or access it from the centrally maintained release area in AFS. o If you choose to use AFS, installation instructions can be found here. * Install Emacs (optional) o If you are familiar with emacs and wish to use this on windows, follow the instructions here.

For the CERN Terminal Server

* Install the appropriate remote desktop software o Installation instructions can be found from here for Windows, Mac and linux users. + Note - rdesktop has already been installed on lxplus.

* Register your CERN NICE account for TS access o This can also be done from here, by following the registration link.

* Start a session on the terminal server cerntsdev01.cern.ch. o For linux the application to use is "rdesktop". A useful set of options (for a British keyboard) is

pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch

* Connection Problems ? o If you experience problems connecting to the Terminal Server from outside CERN, it is possible that your local network is blocking connections through the RDP port 3389. Symptoms are, for example with rdesktop :-

pcdn ~ > rdesktop -d CERN -k en-gb -g 1024x768 -T "NICE TS" cerntsdev01.cern.ch pcdn ~ > ERROR: connect: Connection refused

o If this happens, you should speak to your local system administrator to see if access can be granted. If this is not possible, one solution which works very well is to start a VNC session on lxplus, and run rdesktop from there. See this page for details on how to use VNC.

For both standalone and TS sessions, once you performed the prerequisites as above :-

* Configure SSH access to the CVS repository o Detailed instructions can be found here. o NOTE For Terminal Server users : TS users can not use the "Scheduled Tasks", as described in the notes, since this requires administrator rights. A work around for this is to create a desktop short cut :- + Create a new shortcut on your desktop (right click on the desktop) + Add the command "C:\Program Files\PuTTY\pageant.exe" <path-to-private-key> + Where <path-to-private-key> is the complete path to your private ssh key. o Double clicking this new icon will start up pagent and add you key.

* Create a .emacs file in your HOME area (optional) o Copy to the directory pointed to by the environment variable HOME, your .emacs file. A standard version containing the customisations for LHCb, can be downloaded from here. (NB - Remember to remove the first "a" from the file name when saving. It was added since the web server doesn't like files without a character before the . !) + If you don't have the variable HOME defined, follow the instructions here to define it. + NOTE For Terminal Server users : Emacs is already installed and available from the start Menu.

* If you want to access the AFS software release areas, configure AFS o Using the AFS application (a little padlock in the system tray) :- + Mandatory : Mount /afs as Z: + Recommended : Mount your home (e.g. /afs/cern.ch/user/j/jonrob) area as U:

Define Environment Variables

The following environment variables are mandatory and must be defined (in Start->Control Panel->System->Advanced Menu)

* TEMP o CMT needs to write some temporary files: it writes on %TEMP%. o You should make sure that the TEMP environment variable points to an area with write access. * User_release_area o The first location where CMT is looking for projects. You should create a directory, typically on the local disk ( e.g. C:\cmtuser), and set User_release_area to point to it. o NOTE For Terminal Server users : For local files, we recommend using the directory C:/Users//cmtuser * CVSROOT o Must be set to ":ext:isscvs.cern.ch:/local/reps/lhcb" to enable ssh access to the server.

* CVS_RSH o Must be set to the location of the PuTTy application "plink". Normally this will be "C:\Program Files\PuTTY\plink".

The following variable is optional, it should only be set if you want CMT to access the AFS software release areas

* AFSROOT o Set the environment variable AFSROOT to Z:

The following variables are optional, they are needed if you want to use emacs as editor

* HOME o Points to your "home" area (e.g. C:\Users\ on the TS). Used by emacs as the location to look for a ".emacs" file.

* EMACSDIR o The location of the LHCb Emacs package. Set as "Z:\cern.ch\lhcb\software\releases\TOOLS\Tools\Emacs\pro"

Install a software release (optional)

If you have chosen to not use AFS, you have to install at least one version of the LHCb software stack, using the installProject.py script.

* Create a directory on the local disk under which you will install the software. e.g. C:\releases * Define the environment variable MYSITEROOT to point to the above directory * Import the software by following the instructions given here.

Map Network Drives (optional)

If you have chosen to use the AFS release area, and you are at CERN, we recommend that you map the directory \\cern.ch\dfs\Experiments to the S: drive. This directory contains a collection of scripts needed to run various tasks. To map a network drive, use the Tools menu of the Windows Explorer. Available Commands at the DOS Prompt

(Hint: If you want to have a unix shell style "tab" behaviour to autocomplete a filename/directory in DOS, set the value "9" in the registry key: HKEY_CURRENT_USER\Software\Microsoft\Command Processor\CompletionChar)

When you open a new DOS window, you should execute a script equivalent to the group login on Linux, to set up all other environment variables necessary to work with CVS and CMT. Depending on whether or not you have installed the software locally, you should type:

* %MYSITEROOT%\scripts\localsetup.bat (local installation) * S:\lhcb\scripts\lhcbsetup (AFS+DFS installation)

(Hint: If you have a desktop shortcut to start a DOS window, you can modify its properties to execute the script automatically: right-click on the icon, select Properties, Shortcut tab. In "Target:" append the string: /K S:\lhcb\scripts\lhcbsetup. In "Start in:" you could choose to start in %User_release_area%.)

The following commands are available at the DOS prompt:

* getpack Similar behaviour than the Linux one with the same arguments. It does the checkout from the cvs repository and configures the package. * setenvProject Setup your environment for a particular project (e.g. setenvProject Brunel v31r7). Wildcard usage does not always work - you may need to specify the version you want at the command line. * cmt All cmt commands are available. This include the cmt broadcast, cmt checkout, etc. * make Is equivalent to "nmake /f nmake" * setup To execute the setup.bat in each package to set the necessary environment variables. * cvs Wrapper for the cvs command (accesses the public WinCVS installation in the CERN dfs domain). * doxygen Wrapper for the doxygen documentation tool. See here for details * set Standard DOS command to set environment variables. Useful for setting variables for the current DOS window only. e.g. set User_release_area=C:\cmtuser

Building LHCb Software on Windows in Command Line Mode

Building software in Windows in command-line mode is not much different from building it in Linux. All the basic commands (cmt, cvs, etc.) should just work the same way in this environment. This is perhaps the easiest way to check that your package can be built and run in Windows if you are not used to the graphical integrated development environments (Visual Studio).

The following command sequence should just do the work of building and running (e.g. using Brunel) > BrunelEnv v24r2 > getpack Rec/Brunel v24r2 > cd Rec\Brunel\v24r2\cmt > make (or "cmt broadcast make" for multiple packages) > setup > ..\win32_vc71_dbg\Brunel.exe ..\options\v200402.opts

Using Visual Studio .NET

Note to Terminal Server Users : In order to use the graphical interface to Visual Studio .Net you need special access rights. You should ask Joel to add you to the "Debugger Users" group on the terminal server.

Before starting Visual Studio.NET, you need to create the "solution" file (equivalent to the workspace in VisualStudio 6). For example:

> cd C:\cmtuser\Rec\Brunel\v24r2\cmt > setup > cmt build vsnet > ..\Visual\Brunel.sln

The last command starts Visual Studio.NET. Before running e.g. Brunel, you may have to tell Visual Studio.NET about the job options file that you want to read:

* In Solution Explorer select Brunel * In Project Menu: "Set as StartUp Project" * In Project Menu -> Properties... o Select Debugging the left hand panel o In Command Arguments add: ..\options\v200402.opts

N.B. This step is only necessary once, it is remembered in subsequent Visual Studio.NET sessions with this executable

You are now ready to debug your program. Use [F5] to run the program in debug mode.

Data Access on Windows

If you have installed the Castor client, you can access Castor data files directly from Gaudi, as on Linux. Instructions for accessing data using DC04 software (obsolete) are given here

LHCbTS environment

Local software usage

AFS software usage

Defining your user release area

Installed development tools

-- HubertDegaudenzi - 30 Nov 2007

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback