SSO Logout

Subversion Repositories hepmc

Rev

Rev 360 | Rev 483 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
285 garren 1 
#-------------------------------------------------------------
2 
# installing HepMC
3 
#-------------------------------------------------------------
4 
 
5 
Although it is possible to build the HepMC libraries from this directory,
6 
we recommend that you create a separate build directory and work from there.
7 
 
8 
#-------------------------------------------------------------
9 
#  platform specific issues
10 
#-------------------------------------------------------------
11 
 
12 
To build for Windows Visual C++, configure with CXX=cl CC=cl.
361 garren 13 
To avoid autotool confusion, we recommend running the bootstrap
14 
in your cygwin environment before beginning the build.
360 garren 15 
Notice that custom makefiles are used by the Visual C++ build.
293 garren 16 
See ReadMe.cygwin for more information.
285 garren 17 
 
18 
On MacOSX, you need to define MACOSX_DEPLOYMENT_TARGET appropriately.
19 
For instance, set MACOSX_DEPLOYMENT_TARGET to "10.4" if you
20 
have MacOS 10.4 installed on your system.
21 
 
22 
#-------------------------------------------------------------
23 
#  installing from a source code tar ball
24 
#-------------------------------------------------------------
25 
 
26 
Unwind the source code tar ball in some relevant directory.
27 
Autoconf and automake will aready have been run.
28 
Determine where the files will be installed.
29 
We recommend that you create a separate build directory that is NOT in
30 
the source code directory tree.
31 
 
32 
cd <build_directory>
33 
<source_code_direcotry>/configure --prefix=<install_dir>
34 
   (Note that files will be installed under /usr/local if you do not
35 
    specify a prefix.)
36 
make
37 
   (Build temporary copies of libraries and executables.)
38 
make check
39 
   (Run the tests.)
40 
make install
41 
   (Copy libraries, headers, executables, etc. to relevant
42 
    subdirectories under <install_dir>.)
43 
 
44 
#-------------------------------------------------------------
45 
#  configure options
46 
#-------------------------------------------------------------
47 
 
48 
A variety of options can be given to configure.  Below is a list
49 
of the options that you are likely to find most useful.
50 
 
51 
  --help                  provides a partial list of options
52 
  --prefix=PREFIX         install architecture-independent files in PREFIX
53 
                          [default is /usr/local]
54 
  --disable-shared        build only static libraries
55 
  --disable-static        build only shared libraries
56 
  --enable-visual         on by default when using Visual C++
57 
  --enable-gmake          use gmake (default is make)
58 
  --with-CLHEP            --with-CLHEP=$CLHEP_DIR:
59 
                          CLHEP is used ONLY in the examples
60 
  --with-GENSER           --with-GENSER=$GENSER_DIR:
61 
                          GENSER is used ONLY in the examples
62 
 
63 
#-------------------------------------------------------------
64 
# building from cvs
65 
#-------------------------------------------------------------
66 
 
67 
You will need current versions of automake, autoconf, and libtool.
68 
On some machines, you will need to build them.  See building autotools below.
69 
 
70 
cvs co HepMC
71 
 
72 
cd HepMC
73 
./bootstrap
74 
 
75 
Bootstrap will run doxygen and latex to build the documents.
76 
 
77 
Now continue with directions as if you unpacked a source code tarball.
78 
 
79 
#-------------------------------------------------------------
80 
# building autotools
81 
#-------------------------------------------------------------
82 
 
83 
If you do not have at least autoconf 2.59 and automake 1.9.1, you will
84 
need to build autoconf, automake, and libtool.  On some platforms,
85 
you may also need to build m4 and texinfo.
86 
 
87 
Download the relevant tarballs from gnu.org
88 
(http://www.gnu.org/software/autoconf/, http://www.gnu.org/software/automake/,
89 
and http://www.gnu.org/software/libtool/)
90 
Untar them in a common source code tree.
91 
Decide whether you want to install them in /usr/local or your own
92 
install directory.  If you use your own install directory, use
93 
 
94 
        --prefix=<install_dir>
95 
 
96 
with configure.
97 
 
98 
For each autotool package:
99 
 
100 
     <source_code_dir>/configure [--prefix=<install_dir>]
101 
     make
102 
     make install
103 
 
104 
Make sure that <install_dir>/bin is before /usr/bin in your path.
105 
 
106 
#-------------------------------------------------------------