| 1 |
dnl Process this file with autoconf to produce a configure script. |
| 2 |
|
| 3 |
dnl Define the reference directory checking if the file exist there |
| 4 |
dnl Any file argument can be passed to AC_INIT but, on the same time, |
| 5 |
dnl changing all the relative path for all the files involved in the code! |
| 6 |
dnl this will be called in the all the other MAKEFILEs as "@top_srcdir@" |
| 7 |
AC_INIT(event/PamelaRun.h) |
| 8 |
|
| 9 |
dnl Adds several standard checks. It takes the program name and version number as arguments. |
| 10 |
AM_INIT_AUTOMAKE([yoda],[0.1.0]) |
| 11 |
|
| 12 |
dnl Indicates that you will be using a config.h file |
| 13 |
dnl config.h will be generated by AUTOCONF using a confing.h.in file |
| 14 |
dnl config.h.in can be generated automatically using AUTOHEADER |
| 15 |
dnl However, you need a stamp-h file in your project to ensure that |
| 16 |
dnl AUTOMAKE regenerates config.h from config.h.in. |
| 17 |
dnl Type 'touch stamp-h' to add this file to your project |
| 18 |
AM_CONFIG_HEADER(config.h) |
| 19 |
|
| 20 |
AC_LIBTOOL_DLOPEN |
| 21 |
|
| 22 |
dnl The following macros make the system type available to configure scripts |
| 23 |
AC_CANONICAL_HOST |
| 24 |
|
| 25 |
dnl Indicates that the source code may be in C |
| 26 |
AC_PROG_CC |
| 27 |
|
| 28 |
dnl ------------------Fortran support---------------------------------- |
| 29 |
dnl Determine a Fortran 77 compiler to use. If F77 is not already set in the environment, |
| 30 |
dnl then check for g77 and f77, and then some other names. |
| 31 |
dnl Set the output variable F77 to the name of the compiler found |
| 32 |
AC_PROG_F77(f77 fort77 g77) |
| 33 |
|
| 34 |
dnl Determine the linker flags (e.g., `-L' and `-l') for the Fortran 77 |
| 35 |
dnl intrinsic and run-time libraries that are required to successfully |
| 36 |
dnl link a Fortran 77 program or shared library. |
| 37 |
dnl The output variable FLIBS is set to these flags |
| 38 |
AC_F77_LIBRARY_LDFLAGS |
| 39 |
dnl ------------------Fortran support---------------------------------- |
| 40 |
|
| 41 |
|
| 42 |
dnl Indicates that the source code may be in C++ |
| 43 |
AC_PROG_CXX |
| 44 |
AC_PROG_LIBTOOL |
| 45 |
|
| 46 |
dnl Will generate an install target so that users may just type 'make install' to install the software |
| 47 |
dnl Set output variable INSTALL to the path of a BSD compatible install program, |
| 48 |
dnl if one is found in the current PATH. |
| 49 |
dnl Otherwise, set INSTALL to `dir/install-sh -c', checking the directories specified to |
| 50 |
dnl AC_CONFIG_AUX_DIR (or its default directories) to determine dir |
| 51 |
AC_PROG_INSTALL |
| 52 |
|
| 53 |
dnl This will allow you to build code in sub-directories into temporary libraries, |
| 54 |
dnl which MAKE will then link in with the rest of the code |
| 55 |
AC_PROG_RANLIB |
| 56 |
|
| 57 |
|
| 58 |
AC_PROG_MAKE_SET |
| 59 |
AC_CHECK_PROG(HAS_DOXYFILE, doxygen, yes) |
| 60 |
|
| 61 |
missing_dir=`cd $ac_aux_dir && pwd` |
| 62 |
AM_MISSING_PROG(ACLOCAL, aclocal, $missing_dir) |
| 63 |
AM_MISSING_PROG(AUTOCONF, autoconf, $missing_dir) |
| 64 |
AM_MISSING_PROG(AUTOMAKE, automake, $missing_dir) |
| 65 |
AM_MISSING_PROG(AUTOHEADER, autoheader, $missing_dir) |
| 66 |
AM_MISSING_PROG(MAKEINFO, makeinfo, $missing_dir) |
| 67 |
|
| 68 |
dnl Process the different options |
| 69 |
AC_ARG_WITH(root, |
| 70 |
[--with-root=path Use the specified ROOT directory], |
| 71 |
ROOTSYS=$with_root,) |
| 72 |
|
| 73 |
ROOT_LIBRARY="${ROOTSYS}/lib" |
| 74 |
|
| 75 |
ROOT_LDFLAGS="${ROOT_LIBRARY}/libHist.so ${ROOT_LIBRARY}/libMatrix.so ${ROOT_LIBRARY}/libTree.so ${ROOT_LIBRARY}/libCore.so ${ROOT_LIBRARY}/libCint.so -ldl" |
| 76 |
|
| 77 |
ROOT_INCLUDES="-I${ROOTSYS}/include" |
| 78 |
AC_SUBST(ROOT_INCLUDES) |
| 79 |
AC_SUBST(ROOT_LDFLAGS) |
| 80 |
ROOTCINT=${ROOTSYS}/bin/rootcint |
| 81 |
AC_SUBST(ROOTCINT) |
| 82 |
|
| 83 |
AC_ARG_WITH(log4cppp, |
| 84 |
[--with-log4cpp=path Use the specified directroy for log4cpp], |
| 85 |
LOG4CPP=$with_log4cpp,) |
| 86 |
|
| 87 |
dnl Checks for header files. |
| 88 |
AC_HEADER_STDC |
| 89 |
|
| 90 |
|
| 91 |
dnl Indicates the name of the Makefile which will be generated |
| 92 |
dnl and the various subDirs where it will be generated one |
| 93 |
dnl Add your own Makefiles to create here. |
| 94 |
AC_OUTPUT(Makefile Doxyfile \ |
| 95 |
event/Makefile \ |
| 96 |
dnl ------------------makes for Packets and SubPackets---------------- |
| 97 |
event/mcmd/Makefile \ |
| 98 |
event/tmtc/Makefile \ |
| 99 |
event/log/Makefile \ |
| 100 |
event/arrDump/Makefile \ |
| 101 |
event/tabDump/Makefile \ |
| 102 |
event/varDump/Makefile \ |
| 103 |
event/physics/Makefile \ |
| 104 |
event/physics/tracker/Makefile \ |
| 105 |
event/physics/anticounter/Makefile \ |
| 106 |
event/physics/calorimeter/Makefile \ |
| 107 |
dnl ------------------makes for Packets and SubPackets---------------- |
| 108 |
|
| 109 |
|
| 110 |
dnl ------------------makes for Techmodel Data---------------- |
| 111 |
techmodel/Makefile \ |
| 112 |
techmodel/forroutines/Makefile \ |
| 113 |
techmodel/forroutines/tracker/Makefile \ |
| 114 |
techmodel/forroutines/tracker/readraw/Makefile \ |
| 115 |
techmodel/forroutines/anticounter/Makefile \ |
| 116 |
techmodel/forroutines/calorimeter/Makefile \ |
| 117 |
techmodel/physics/Makefile \ |
| 118 |
dnl ------------------makes for Techmodel Data---------------- |
| 119 |
|
| 120 |
|
| 121 |
) |
| 122 |
|
| 123 |
|
Parent Directory
| 
Revision Log