Page Menu
Home
HEPForge
Search
Configure Global Search
Log In
Files
F11222325
INSTALL
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Flag For Later
Size
10 KB
Subscribers
None
INSTALL
View Options
#-------------------------------------------------------------
# Installing WHIZARD
#-------------------------------------------------------------
Although it is possible to build the WHIZARD libraries from this directory,
we recommend that you create a separate build directory and work from there.
#-------------------------------------------------------------
# Installing from a source code tar ball
#-------------------------------------------------------------
WHIZARD is Free Software and the sources can be obtained either from
http://whizard.event-generator.org
or the HepForge repository:
http://projects.hepforge.org/whizard
The command
gzip -cd whizard-2.X.X.tgz | tar xf -
will unpack the sources in a subdirectory whizard-2.X.X,
where XX is the current version number.
Prerequisites are:
- Make
- Objective Caml compiler
- Fortran 95/03 compiler
- C/C++ (for HepMC interfaces)
The Objective Caml (O'Caml) compiler is available from
http://pauillac.inria.fr/ocaml/
#-------------------------------------------------------------
# External libraries and programs
#-------------------------------------------------------------
The following external libraries and programs can be linked to
WHIZARD:
-- LHAPDF for proton, pion and photon structure functions.
You can get it from: http://projects.hepforge.org/lhapdf
-- HepMC for the corresponding event file standard.
Available from: http://lcgapp.cern.ch/project/simu/HepMC
-- Other external programs like PYTHIA and HERWIG for parton
showering and hadronization can be included in a standard
way by passing LHEF or HepMC event files to them.
-- ROOT and DELPHES will be provided shortly.
-- A preliminary interface to FeynRules exists and will be
ready for general use soon.
#-------------------------------------------------------------
# platform specific issues
#-------------------------------------------------------------
MAC OS X:
WHIZARD has been tested and partially developed under MAC OS X
Darwin 9.6.0-9.8.0 (Leopard) and Darwin 10.0.0-10.2.0 (Snow
Leopard). The single pass linker here forces to explicitly include
static C++ libraries when externally linking HepMC. The necessary
flags are automatically taken care of by the configure script.
#-------------------------------------------------------------
# installing from a source code tar ball
#-------------------------------------------------------------
Unwind the source code tar ball in some relevant directory.
Autoconf and automake will already have been run.
Determine where the files will be installed.
We recommend that you create a separate build directory that is NOT in
the source code directory tree.
cd <build_directory>
<source_code_directory>/configure --prefix=<install_dir>
(Note that files will be installed under /usr/local if you do not
specify a prefix.)
make
(Build temporary copies of libraries and executables.)
make check [optional]
(Perform sanity checks and standard tests)
make install
(Copy libraries, headers, executables, etc. to relevant
subdirectories under <install_dir>.)
#-------------------------------------------------------------
# configure options
#-------------------------------------------------------------
A variety of options can be given to configure. Below is a list
of the options that you are likely to find most useful.
Defaults for the options are specified in brackets.
Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print `checking...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or `..']
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr/local]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc. You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.
For better control, use the options below.
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/whizard]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names
System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
Optional Features:
--disable-option-checking ignore unrecognized --enable/--with options
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-shared[=PKGS] build shared libraries [default=yes]
--enable-static[=PKGS] build static libraries [default=yes]
--enable-fast-install[=PKGS]
optimize for fast installation [default=yes]
--disable-dependency-tracking speeds up one-time build
--enable-dependency-tracking do not reject slow dependency extractors
--disable-libtool-lock avoid locking (might break parallel builds)
--enable-dl enable libdl for creating/loading process libraries
on-the-fly [[yes]]
--disable-noweb disable the noweb programs, even if available [[no]]
--enable-fc-quadruple use quadruple precision in Fortran code [[no]]
--enable-fc-profiling use profiling for the Fortran code [[no]]
--enable-fc-impure compile Omega libraries impure [[no]]
--disable-ocaml disable the OCaml parts, even if OCaml available
[[no]]
--enable-lhapdf enable LHAPDF for structure functions [[yes]]
--enable-hepmc enable HepMC for handling event data [[yes]]
--enable-stdhep enable STDHEP for binary event files [[yes]]
--enable-optimization-for-parameter-files
enable (useless) optimization for parameter file
[[no]]
--disable-default-checks
disable the default self-checks [[no]]
--enable-extnum-checks enable time-consuming extensive SM, SUSY and models
checks [[no]]
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-pic try to use only PIC/non-PIC objects [default=use
both]
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
LIBS libraries to pass to the linker, e.g. -l<library>
CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
CPP C preprocessor
FC Fortran compiler command
FCFLAGS Fortran compiler flags
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CXXCPP C++ preprocessor
#-------------------------------------------------------------
# building from svn (developper version)
#-------------------------------------------------------------
You will need current versions of automake and autoconf. On some machines,
you will need to build them. See building autotools below. Furthermore,
you need to have noweb to be installed for the developer version from the
svn repository. To build the documentations, LaTeX, MetaPost and OcamlWeb
are also necessary tools. Although the first two are quite standard, you
can get them from http://www.tug.org/texlive/. Follow the instructions there.
OcamlWeb is available from http://www.lri.fr/~filliatr/ocamlweb/.
The check out can be done in that way:
svn co svn.hepforge.org/hepforge/home/whizard/event-generators/whizard/trunk
cd trunk
autoreconf
Now continue with directions as if you unpacked a source code tarball.
#-------------------------------------------------------------
# building autotools
#-------------------------------------------------------------
If you do not have at least autoconf 2.60 and automake 1.10, you will
need to build autoconf and automake. On some platforms, you may also
need to build m4 and texinfo.
Download the relevant tarballs from gnu.org
(http://www.gnu.org/software/autoconf/, http://www.gnu.org/software/automake/).
Untar them in a common source code tree.
Decide whether you want to install them in /usr/local or your own
install directory. If you use your own install directory, use
--prefix=<install_dir>
with configure.
For each autotool package:
<source_code_dir>/configure [--prefix=<install_dir>]
make
make install
Make sure that <install_dir>/bin is before /usr/bin in your path.
#-------------------------------------------------------------
# getting and installing noweb
#-------------------------------------------------------------
Noweb can be accessed from here:
http://www.cs.tufts.edu/~nr/noweb/
Untar the source code. Go to the src/ subdirectory of the unpacked noweb
source code. Follow the instructions from the INSTALL file. You have to
specify binary, install and TeX paths explicitly, unfortunately. After a
make install
you probably have to copy the binaries into a directory which is in your
executable path.
#-------------------------------------------------------------
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Wed, May 14, 11:46 AM (5 h, 15 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
5093478
Default Alt Text
INSTALL (10 KB)
Attached To
rWHIZARDSVN whizardsvn
Event Timeline
Log In to Comment