Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Standalone Windows Distribution

If you do not want to build SLIC yourself, there is a Windows executable available for download.

The current version is available as a ZIP file containing a static binary and the required DLLs.

Download the ZIP file using your browser and unzip the contents to C:. You should see the directory C:\slic_win32.

Test out the binary by running it in a console window.

  1. Start -> Run -> cmd.
  2. Press ENTER.
  3. Go to the SLIC directory.
    No Format
    
    C:\
    cd slic_win32
    
  4. Execute SLIC from the command line.
    No Format
    
    slic
    
Warning

Close all Cygwin windows before running SLIC, or the packaged Cygwin DLL will not load properly.

The Xerces and Cygwin DLLs are also included so that the package is standalone.

Info

Cygwin needs to be installed to run SLIC.

Download the SLIC Windows binary from this location.

http://www.lcsim.org/dist/slic/slic-current-WIN32-g%2B%2B-bin.tar.gz

Open a Cygwin window and go to the directory where you saved the tarball.

Untar the file after it is saved to your computer.

No Format

tar -zxvf slic-current-WIN32-g++-bin.tar.gz

Now test the binary.

No Format

cd SimDist
./scripts/slic.sh

The slic usage screen should show.

Preliminary Setup for Installation

...

  1. Download the Cygwin setup program.
  2. Double-click on it and click Next.
  3. Select Install from Internet and click Next.
  4. Enter your preferred Root Directory and click Next.
  5. Enter your preferred Local Package Directory, which can be the same as the Root Directory, and then click Next.
  6. Select Direct Connection and click Next.
  7. Select a site from the Available Download Sites. Servers inside your country will probably be fastest. I use ftp://ftp.sunsite.utk.edu.
  8. Click Next.
  9. In the Cygwin Setup - Select Packages window, you need to make sure that the following tools are selected by clicking in the corresponding box under the New column until you see a version number.
    1. Required packages.
      • Devel -> cvs
      • Devel -> gcc-core
      • Devel -> gcc-g++
      • Devel -> make
      • Base -> gzip
      • Base -> tar
    2. If OpenGL visualization is being used, these should also be installed.
      • X11 -> ALL
      • Graphics -> OpenGL
    3. Tool for downloading package tarballs and zip files.
      • Web ->
      Tool for downloading package tarballs and zip files.
      • Web -> wget
  10. Click Next after you have selected the packages.
  11. Cygwin will now automatically download and install all the selected packages. It might take awhile, so now is the time to go get some coffee.
  12. If desired, select Create icon on Desktop or Add icon to Start Menu, and click Finish.
Tip
titleCygwin Packages

It may be easier to simply install all Cygwin packages instead of selecting them individually.

If you need additional information on this installation process, Norman Graf has more detailed Cygwin installation instructions.

...

Package Installations

CLHEP

CLHEP has installation instructions for version 1.9 and up. But you (http://wwwasd.web.cern.ch/wwwasd/lhc\+\+/clhep/INSTALLATION/newCLHEP-install.html) for version 1.9 and up. But you should not need them to setup the package.

...

  1. Return to the work dir, create a Geant4 subdir and go into it.
    No Format
    cd $sim_work
    mkdir geant4
    cd geant4
    
  2. Download the Geant4 tarball.
    No Format
    wget http://geant4.cern.ch/geant4/source/source/geant4.7.1.tar.gz
    
  3. Unzip it.
    No Format
    tar -zxvf geant4.7.1.tar.gz
    
  4. Set the following variables in setup.sh. (You should not need to run Geant4's Configure script.)
    No Format
    export G4INSTALL=${sim_work}/geant4/geant4.7.1
    export G4SYSTEM=WIN32-g++
    
  5. Go into the Geant4 base dir.
    No Format
    
    cd geant4.7.1
    
  6. Build the libraries, which will be placed at $G4INSTALL/lib/WIN32-g++. (This could take up to a few hours depending on your machine.)
    No Format
    
    cd source
    make
    
  7. Install the headers into $G4INSTALL/include.
    No Format
    
    make includes
    
  8. If you would like to enable OpenGL visualization, add the following variable definitions.
    This assumes you installed the X11 libraries when you set up cygwin.
    No Format
    
    export OGLHOME=/usr/X11R6
    export G4VIS_BUILD_OPENGLX_DRIVER=1
    export G4VIS_USE_OPENGLX=1
    
  9. Go into the Geant4 base dirBuild the physics list libraries. These will go into $G4INSTALL/lib/plists/WIN32-g++.
    No Format
    cd geant4../physics_lists/hadronic
    make
    

Hopefully, Geant4 has been installed successfully, and you don't have too many more gray hairs.

LCPhys

SLIC requires a special physics list written by Dennis Wright for Linear Collider physics.

  1. 7.1
    
  2. LCPhys requires that a special flag is set in order to use the latest Kaon model. At the end of config/architecture.gmk, insert the following line exactly as it appears below:
    No Format
    
    CPPFLAGS += -DG4BERTINI_KAON
    
    Hopefully, this hack will be remedied soon!
  3. Now for another lovely Geant4 hack. In order to successfully compile the HepRep driver, the following line in the file config/sys
  4. Go back to the work dir.
    No Format
    
    cd $sim_work
    
  5. Checkout the physics list from CVS.
    No Format
    
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd checkout LCPhys
    
  6. Assuming that the environment from the Geant4 installation is still in place, you can build this like any other physics list, and the library should be installed into $G4INSTALL/lib/plists/WIN32-g++.gmk
    No Format
    cd LCPhys
    make
    
    Set the LCPhys variable in setup.sh.
    CXXFLAGS  := -Wall -ansi -pedantic -pipe
    
    should be replaced with
    No Format
    export LCPHYS_BASE=$sim_work/LCPhys
    

LCIO

LCIO provides binary output capabilities.

Warning

Installation requires a working Java runtime for ant support.

LCIO has a very nice manual with a whole section on installation. Thanks, Frank!

I will still walk you through the basic procedure.

  1. CXXFLAGS  := -W -Wall -ansi -pedantic -Wno-non-virtual-dtor -Wno-long-long
    CXXFLAGS  += -Wwrite-strings -Wpointer-arith -Woverloaded-virtual -pipe 
    
  2. Build the libraries, which will be placed at $G4INSTALL/lib/WIN32-g++. (This could take up to a few hours depending on your machine.)
    No Format
    
    cd source
    make
    
  3. Install the headers into $G4INSTALL/include.
    No Format
    
    make includes
    
  4. Build the physics list libraries. These will go into $G4INSTALL/lib/plists/WIN32-g++.
    No Format
    
    cd ../physics_lists/hadronic
    make
    

Hopefully, Geant4 has been installed successfully, and you don't have too many more gray hairs.

LCPhys

SLIC requires a special physics list written by Dennis Wright for Linear Collider physics.

  1. Go back to the work dir.
    No Format
    
    cd $sim_work
    
  2. Checkout the physics list from CVS.
    No Format
    
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd checkout LCPhys
    
  3. Assuming that the environment from the Geant4 installation is still in place, you can build this like any other physics list, and the library should be installed into $G4INSTALL/lib/plists/WIN32-g++.
    No Format
    
    cd LCPhys
    make
    
  4. Set the LCPhys variable in setup.sh.
    No Format
    
    export LCPHYS_BASE=$sim_work/LCPhys
    

LCIO

LCIO provides binary output capabilities.

Warning

Installation requires a working Java runtime for ant support.

LCIO has a very nice manual with a whole section on installation. Thanks, Frank!

I will still walk you through the basic procedure.

  1. Go back to the work dir.
    No Format
    
    cd $sim_work
    
  2. Checkout LCIO from CVS.
    No Format
    
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcio checkout lcio
    
  3. Add these lines to your setup.sh.
    No Format
    
    export LCIO=${sim_work}/lcio 
    export PATH=$LCIO/tools:$LCIO/bin:$PATH
    
  4. Build the libraries using the bundled aid and ant tools.
    No Format
    
    cd lcio
    ant aid.generate cpp
    

Xerces-C++

  1. Go back to the work dir, create a subdir for Xerces-C++, and go into it.
    No Format
    
    cd $sim_work
    mkdir xercesc
    cd xercesc
    
  2. Download the Xerces tarball.
    No Format
    
    wget http://www.apache.org/dist/xml/xerces-c/xerces-c-src_2_6_0.tar.gz
    
  3. Unzip the tarball.
    No Format
    
    tar -zxvf xerces-c-src_2_6_0.tar.gz
    
  4. Set XERCESCROOT for the build in your environment, only
  5. Go back to the work dir.
    No Format
    
    cd $sim_work
    
  6. Checkout LCIO from CVS.
    No Format
    
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcio checkout lcio
    
  7. Add these lines to your setup.sh.
    No Format
    export LCIOXERCESCROOT=${sim_work}/lcio 
    export PATH=$LCIO/tools:$LCIO/bin:$PATH
    
  8. Build the libraries using the bundled aid and ant tools.
    No Format
    
    cd lcio
    ant aid.generate cpp
    

Xerces-C++

  1. xercesc/xerces-c-src_2_6_0
    
  2. Go into the Go back to the work dir, create a subdir for Xerces-C++ , and go into itbuild area.
    No Format
    cd $sim_work
    mkdir xercesc
    cd xerces-c-src_2_6_0/src/xercesc
    
    Download
  3. Configure the Xerces tarballbuild.
    No Format
    wget http://www.apache.org/dist/xml/xerces-c/xerces-c-src_2_6_0.tar.gz
    
  4. Unzip the tarball.
    No Format
    
    tar -zxvf xerces-c-src_2_6_0.tar.gz
    
  5. /runConfigure -pcygwin -cgcc -xg++ \
    -minmem -nsocket -tnative -rpthread \
    -P `cd ../../..; pwd`
    
  6. Build and install it.
    No Format
    
    make
    make install
    
  7. In setup.sh, set XERCESCROOT to the installation area and add the DLL location to the PATHSet XERCESCROOT for the build in your environment, only.
    No Format
    export XERCESCROOT=${sim_work}/xercesc/xerces-c-src_2_6_0
    
    Go into
    
    export PATH=$XERCESCROOT/bin:$PATH
    
Tip

When rebuilding Xerces-C++, which you will probably not need to do once you get it working, XERCESCROOT needs to be set back to the Xerces-C++

...

source area rather than the installation base.

No Format

cd xerces-c-src_2_6_0/src/xercesc

GDML

GDML's CVS is not directly accessible from the command line, but a tarball is available through a WWW interface.

  1. Download a snapshot of the current CVS head using this link in your browser: http://simu.cvs.cern.ch/cgi-bin/simu.cgi/simu/GDML2/GDML2.tar.gz?tarball=1.
    • Save the tarball to sim_wrk, which should be C:\sim.
  2. Unzip the tarball.
    No Format
    
    tar -zxvf GDML2.tar.gz
    
  3. Change into the CPPGDML directory.
    No Format
    
    cd GDML2/CPPGDML
    
  4. Set GDML_BASE in setup.sh.
    No Format
    
    export GDML_BASE=${sim_work}/GDML2/CPPGDML
    
  5. Configure the build.
    No Format
    
    ./configure --enable-shared-libs=no
    
  6. Build it.
    No Format
    
    make
    

LCDD

  1. Go to the work dir and checkout LCDD.
    No Format
    
    cd ${sim_work}
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd checkout lcdd
    
  2. Go into the LCDD dir.
    No Format
    
    cd lcdd
    
  3. Configure the build.
    No Format
    
    ./configure
    
  4. Build the library.
    No Format
    
    make
    
  5. Set the LCDD_BASE variable

...

No Format

./runConfigure -pcygwin -cgcc -xg++ \
-minmem -nsocket -tnative -rpthread \
-P `cd ../../..; pwd`

...

No Format

make
make install

...

No Format

export XERCESCROOT=${sim_work}/xercesc
export PATH=$XERCESCROOT/bin:$PATH
Tip

When rebuilding Xerces-C++, which you will probably not need to do once you get it working, XERCESCROOT needs to be set back to the Xerces-C++ source area rather than the installation base.

GDML

GDML's CVS is not directly accessible from the command line, but a tarball is available through a WWW interface.

  1. Download a snapshot of the current CVS head using this link in your browser: http://simu.cvs.cern.ch/cgi-bin/simu.cgi/simu/GDML2/GDML2.tar.gz?tarball=1.
    • Save the tarball to sim_wrk, which should be C:\sim.
  2. Unzip the tarball.
    No Format
    
    tar -zxvf GDML2.tar.gz
    
  3. Change into the CPPGDML directory.
    No Format
    
    cd GDML2/CPPGDML
    
  4. Set GDML_BASE in setup.sh.
    No Format
    export GDMLLCDD_BASE=${sim_work}/GDML2/CPPGDMLlcdd
    
  5. Configure the build.
    No Format
    
    ./configure --enable-shared-libs=no
    
  6. Build it.
    No Format
    
    make
    

...

SLIC

Finally, you are ready to install the simulation "hub" package. After this, you will have a fully-featured Geant4 simulator on your Windows machine.

  1. Go to the work dir and checkout LCDDSLIC.
    No Format
    cd ${sim_work}
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd checkout lcddslic
    
  2. Go into the LCDD SLIC dir.
    No Format
    cd lcddslic
    
    Configure the build
  3. Set the SLIC_BASE variable in setup.sh.
    No Format
    ./configure
    export SLIC_BASE=${sim_work}/slic
    
  4. Configure the buildBuild the library.
    No Format
    make./configure
    
    Set the
  5. LCDD_BASE variable in setup.shBuild the binary (note that we currently do not support visualization).
    No Format
    export LCDDG4VIS_BASE=${sim_work}/lcdd
    

SLIC

Finally, you are ready to install the simulation "hub" package. After this, you will have a fully-featured Geant4 simulator on your Windows machine.

  1. NONE=1
    make all
    

If the build completes successfully, you should see SLIC's usage statement from the test run.

Running SLIC after Installation

When you want to run later in a Cygwin shell, $XERCESCROOT/bin should be in the PATH, so that Windows can find the DLL at runtime. Since the other applications were linked-in statically, this should be the only setup requirement.

This is the procedure for running SLIC from the Cygwin commandline.

  1. Select Start -> Programs -> Cygwin -> Cygwin Bash Shell.
  2. Add Xerces-C++ bin to the path
  3. Go to the work dir and checkout SLIC.
    No Format
    
    cd ${sim_work}
    cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd checkout slic
    
  4. Go into the SLIC dir.
    No Format
    
    cd slic
    
  5. Set the SLIC_BASE variable in setup.sh.
    No Format
    export SLIC_BASE=${sim_work}/slic
    
  6. Configure the build.
    No Format
    
    ./configure
    
  7. PATH=/cygdrive/c/sim/xerces/bin:$PATH
    
  8. Go to the SLIC directoryBuild the binary (note that we currently do not support visualization).
    No Format
    export G4VIS_NONE=1
    make all
    

If the build completes successfully, you should see SLIC's usage statement from the test run.

Running SLIC after Installation

When you want to run later in a Cygwin shell, $XERCESCROOT/bin should be in the PATH, so that Windows can find the DLL at runtime. Since the other applications were linked-in statically, this should be the only setup requirement.

This is the procedure for running SLIC from the Cygwin commandline.

  1. Select Start -> Programs -> Cygwin -> Cygwin Bash Shell.
  2. Add Xerces-C++ bin to the path.
    No Format
    
    export PATH=/cygdrive/c/sim/xerces/bin:$PATH
    
  3. Go to the SLIC directory.
    No Format
    
    cd /cygdrive/c/sim/slic
    
  4. Run the executable.
    No Format
    
    bin/WIN32-g++/slic [options]
    
  1. cd /cygdrive/c/sim/slic
    
  2. Run the executable.
    No Format
    
    bin/WIN32-g++/slic [options]
    

If you receive an error message about a missing DLL cygxerces-c26.dll, then make sure that the PATH is setup correctly and Xerces-C++ was properly installed.

Warning

If you encounter difficulties running macros, it may be due to the different DOS and Unix end-of-line definitions. You can convert files using:

No Format

dos2unix mymacro.mac

In order to run with OpenGL visualization, an X-server needs to be running on your machine.

This command will start the Cygwin X-server.

No Format

startxwin.sh

Then you need to run SLIC from the xterm that pops-up. At least on my setup, it does not work to run the binary from the plain Cygwin windowIf you receive an error message about a missing DLL cygxerces-c26.dll, then make sure that the PATH is setup correctly and Xerces-C++ was properly installed.

Final Setup Script

The final version of setup.sh (without OpenGL visualization) should be similar to this.

...

If you think this guide could be improved in any way, then please contact the author

Links