| [1337] | 1 | $Id: 00README,v 1.5 2006/08/09 06:26:23 kmura Exp $
|
|---|
| 2 | ==========================================================================
|
|---|
| 3 | Geant4Py
|
|---|
| 4 |
|
|---|
| 5 | Geant4Py is a set of python modules for using Geant4.
|
|---|
| 6 |
|
|---|
| 7 | Tools package
|
|---|
| 8 |
|
|---|
| 9 | In dafault situation, Geant4 creates and uses "granular static libraries".
|
|---|
| 10 | But, Python interface requires "global shared library".
|
|---|
| 11 | This directory contains some utility tools for helping build
|
|---|
| 12 | Geant4 environment for using Python interface.
|
|---|
| 13 | ==========================================================================
|
|---|
| 14 |
|
|---|
| 15 | env
|
|---|
| 16 | ---
|
|---|
| 17 | Additonal setup script for co-building global shared libraries
|
|---|
| 18 |
|
|---|
| 19 | A small setup script helps co-build global shared libraries,
|
|---|
| 20 | in addition to an existing granular static environment.
|
|---|
| 21 |
|
|---|
| 22 |
|
|---|
| 23 | g4autobuild
|
|---|
| 24 | -----------
|
|---|
| 25 | An automatic build tool. The tool takes care of multiple Geant4/CLHEP instances
|
|---|
| 26 | (granular static libray, global static library and global shared library),
|
|---|
| 27 | configuring visualization and UI environments. The building procedures
|
|---|
| 28 | are fully automated, avoiding duplicated building processes.
|
|---|
| 29 |
|
|---|
| 30 | A sample configuration file is as follows;
|
|---|
| 31 | ---------------------------------------------------------------------
|
|---|
| 32 | #
|
|---|
| 33 | # G4SYS
|
|---|
| 34 | #
|
|---|
| 35 | G4SYS Linux-g++
|
|---|
| 36 |
|
|---|
| 37 | #
|
|---|
| 38 | # Base directory of Geant4 builds
|
|---|
| 39 | #
|
|---|
| 40 | G4BASE /opt/heplib/Geant4
|
|---|
| 41 |
|
|---|
| 42 | #
|
|---|
| 43 | # Base directory of CLHEP
|
|---|
| 44 | #
|
|---|
| 45 | CLHEPBASE /opt/heplib/CLHEP
|
|---|
| 46 |
|
|---|
| 47 | #
|
|---|
| 48 | # G4 version and CLHEP version (starting with "-")
|
|---|
| 49 | #
|
|---|
| 50 | # G4 version CLHEP version
|
|---|
| 51 | - geant4.8.1.p01 2.0.2.3
|
|---|
| 52 | - geant4.8.1 2.0.2.3
|
|---|
| 53 |
|
|---|
| 54 | #
|
|---|
| 55 | # Visualization Options (starting with "v")
|
|---|
| 56 | # G4VIS_BUILD_XXX_DRIVER and G4VIS_USE_XXX are activated.
|
|---|
| 57 | #
|
|---|
| 58 | v DAWN
|
|---|
| 59 | v VRML
|
|---|
| 60 | v RAYTRACERX_DRIVER
|
|---|
| 61 | v OPENGLX
|
|---|
| 62 |
|
|---|
| 63 | #
|
|---|
| 64 | # UI Options (starting with "u")
|
|---|
| 65 | # G4UI_USE_XXX is activated.
|
|---|
| 66 | #
|
|---|
| 67 | u TCSH
|
|---|
| 68 | u GAG
|
|---|
| 69 | ---------------------------------------------------------------------
|
|---|
| 70 |
|
|---|
| 71 | Users just specify the base directories of Geant4 and CLHEP,
|
|---|
| 72 | and give combinations of their versions.
|
|---|
| 73 |
|
|---|
| 74 | Then, type
|
|---|
| 75 |
|
|---|
| 76 | $ ./g4autobuild
|
|---|
| 77 |
|
|---|
| 78 | . A series of building processes will start.
|
|---|
| 79 |
|
|---|
| 80 | The "status" directory will be created by the script. Note that null files
|
|---|
| 81 | (named geant4-%version%-xxx) associated with tasks will be created in this
|
|---|
| 82 | directory after finishing each task. These files works as flags for task status.
|
|---|
| 83 |
|
|---|
| 84 |
|
|---|
| 85 | g4package
|
|---|
| 86 | ---------
|
|---|
| 87 | A packaging tool. CLHEP and Geant4 libraries and headers are packed into
|
|---|
| 88 | a specified directory. This script contains a special care for embedded
|
|---|
| 89 | MacOSX(Mach-O) library paths. Using the packaged libraries makes free from
|
|---|
| 90 | setting DYLD_LIBRARY_PATH in MacOSX, especially for CLHEP.
|
|---|
| 91 |
|
|---|
| 92 | For example, on MacOSX,
|
|---|
| 93 |
|
|---|
| 94 | $ ./g4pack --with-g4system=Darwin-g++ \
|
|---|
| 95 | --with-g4-dir=/opt/heplib/Geant4/geant4.8.1.p01 \
|
|---|
| 96 | --with-clhep-dir=/opt/heplib/CLHEP/2.0.2.3 \
|
|---|
| 97 | --with-install-dir=/Library/Frameworks/Geant4.framework/Versions/8.1.1
|
|---|
| 98 |
|
|---|
| 99 | creates new package in a "g4" directory. Then you can copy it to the framework
|
|---|
| 100 | directory specified.
|
|---|
| 101 |
|
|---|
