5 #############################################################################
6 # alibtool - a shell script to help makeing modules for AliRoot Makefile
7 #############################################################################
11 # Revision 1.9 2004/06/18 10:30:54 rdm
12 # fix typo in comment.
14 # Revision 1.8 2004/06/03 23:41:51 rdm
15 # wrap some insanely long lines into mulitple lines.
17 # Revision 1.7 2003/11/10 15:02:38 rdm
18 # re-direct warnings of rmkdepend about not found system include files
19 # to /dev/null. Only generate dependencies on ROOT and AliRoot, not on
20 # system or compiler specific files.
22 # Revision 1.6 2003/07/13 09:26:14 hristov
25 # Revision 1.5 2003/05/02 15:11:52 hristov
26 # Changes to avoid warnings (I.Hrivnacova)
28 # Revision 1.4 2002/10/14 14:57:45 hristov
29 # Merging the VirtualMC branch to the main development branch (HEAD)
31 # Revision 1.3.6.1 2002/07/09 12:24:49 alibrary
32 # Corrections for new MC
34 # Revision 1.3 2002/02/22 07:57:35 alibrary
35 # Reduce verbose output
37 # Revision 1.2 2001/11/14 17:52:48 hristov
38 # Updated version of the flat makefiles (J.-E.Revsbech)
40 # Revision 1.1 2001/10/09 13:45:57 hristov
45 # alibtool <command> <commandparameters>
47 # command must be one of the following:
56 # This scipts is called with a primary command and a command parameter.
57 # It generates output on stdout, so normally it is called with a redirection,
60 # alibtool mkmodule STEER > STEER/module.mk
62 # The command is one of the following:
65 # Makes the dependencies for the file specified as second argument
66 # (for c and cxx files)
69 # Makes the dependencies for the file specified as second argument
73 # Creates the module.mk for the the given directory specified as
78 # When alibtool is called with the mkmodule command it searches the directory
79 # given as the second argument for files called *.pkg. If a file (possibly
80 # several) is found, it will create a file called module.mk based on these
81 # files. For example if running alibtool mkmodule STEER, it will search the
82 # STEER directory and create STEER/module.mk based on all .pkg files is
83 # STEER directory. If a file called libSTEER.pkg is found, then module.mk
84 # will have a section devoted to makeing library libSTEER.so with alle the
85 # sourcefiles specified in libSTEER.pkg. If a file called binSTEER.pkg is
86 # found the module.mk file will create an executable called STEER. Several
87 # *.pkg files can be placed in the same directory. The module.mk files is
88 # created on background of build/header.tpl and build/module.mk by variable
89 # substituion of variables @MODULE@ @PACKAGE@ and @TYPE@.
94 # The syntax for the pkg file is very simple. You specify the sources, headers
95 # and possibly extra include or link options. The *.pkg files is just
96 # inserted "as is" in the module.mk file, so normal Makefile syntax can
97 # be used. These variables can be specified: SRCS, FSRCS, CSRCS, HDRS, CHDRS,
98 # DHDR, EINCLUDE, ELIBS, ELIBSDIR, PACKFFLAGS, PACKCFLAGS, PACKCXXFLAGS.
99 # The first five is just the C++ sources, fortran sources, C sources,
100 # C++ headers and C headers. DHDR is the dictionary header and is the
101 # LinkDef file. EINCLUDE, ELIBS and ELIBSDIR is extra includedirs,
102 # libraries and library search paths. If for example a binary is to be
103 # linked against the variable ELIBSDIR would be set to lib/tgt_$ALICE_TARGET.
104 # Notice that -L and -l is not needed. If the PACKFFLAGS, PACKCFLAGS or
105 # PACKCXXFLAGS is not set it will be set to the default options (set in
106 # config/Makefile.$ALICE_TARGET. For example on Linux GEANT321 has to be
107 # compiled without -O options, so a line like
108 # PACKFFLAGS := $(filter-out -O%,$(FFLAGS))
114 # If alibtool is called with the depend command it will generate a dependecy
115 # file for the sourcefile given as second argument. This only goes for C++
116 # and C files. If dependencies for fortran-fiels is needed, call alibtool
117 # with command dependF. The dependencies are made with rmkdepend.
122 # The same as depend, but for fortran files.
125 ###########################################################################
131 rmkdepend -f- -Y -w 3000 -- $* 2>/dev/null | sed -e "s@^\(.*\)\/\(.*\)\.o:@\1\/tgt_${ALICE_TARGET}\/\2.d \1\/tgt_${ALICE_TARGET}/\\2.o:@" -e 's@^#.*$@@' -e '/^$/d'
136 rmkdepend -f- -Y -w 3000 -- $* 2>/dev/null | sed -e "s@^\(.*\)\/\(.*\)\.o:@\1\/tgt_${ALICE_TARGET}\/\2.d \1\/tgt_${ALICE_TARGET}/\\2.o:@" -e 's@^#.*$@@' -e '/^$/d'
142 #This one gets all the library pkg files
143 tempo=`find ${module} -name "lib*.pkg" | sed -e "sQ${module}/libQQ" -e "sQ\.pkgQQ"`
145 echo "#**************************************************************************";
146 echo "#**** This file is automatically generated from the mkmodules script *****";
147 echo "#**** DO NOT EDIT!! *****";
148 echo "#**************************************************************************";
156 #This one gets all the binary(executable) pkg files
157 tempo=`find ${module} -name "bin*.pkg" | sed -e "sQ${module}/binQQ" -e "sQ\.pkgQQ"`
165 #Now make general bottom for every module (Clean and so on)
166 cat build/clean.tpl | sed -e "sQ\@MODULE@Q${module}Qg"
171 file=$module/$type$i.pkg
172 cat build/header.tpl | sed -e "sQ\@MODULE@Q${module}Qg" -e "sQ@PACKAGE@Q${package}Qg" -e "sQ\@TYPE@Q${type}Qg"
176 cat build/module.tpl | sed -e "sQ\@MODULE@Q${module}Qg" -e "sQ@PACKAGE@Q${package}Qg" -e "sQ\@TYPE@Q${type}Qg"