5 #############################################################################
6 # alibtool - a shell script to help makeing modules for AliRoot Makefile
7 #############################################################################
11 # Revision 1.6 2003/07/13 09:26:14 hristov
14 # Revision 1.5 2003/05/02 15:11:52 hristov
15 # Changes to avoid warnings (I.Hrivnacova)
17 # Revision 1.4 2002/10/14 14:57:45 hristov
18 # Merging the VirtualMC branch to the main development branch (HEAD)
20 # Revision 1.3.6.1 2002/07/09 12:24:49 alibrary
21 # Corrections for new MC
23 # Revision 1.3 2002/02/22 07:57:35 alibrary
24 # Reduce verbose output
26 # Revision 1.2 2001/11/14 17:52:48 hristov
27 # Updated version of the flat makefiles (J.-E.Revsbech)
29 # Revision 1.1 2001/10/09 13:45:57 hristov
34 # alirun <command> <commandparameters>
36 # command must be one of the following:
45 # This scipts is called with a primary command and a commandparameter. It generates output on stdout, so normally it is called with a redirection like
47 # alibtool mkmodule STEER > STEER/module.mk
49 # The command is one of the following
52 # Makes the dependencies for the file specified as second argument (c and cxx files)
55 # Makes the dependencies for the file specified as second argument (fortran files)
58 # Creates the module.mk for the the given directory specified as the second argument.
62 # When alibtool is called with the mkmodule command it searches the directory given as the second argument for files called *.pkg. If a file (possibly several) is found, it will create a file called module.mk based on these files. For example if running alibtool mkmodule STEER, it will search the STEER directory and create STEER/module.mk based on all .pkg files is STEER directory. If a file called libSTEER.pkg is found, then module.mk will have a section devoted to makeing library libSTEER.so with alle the sourcefiles specified in libSTEER.pkg. If a file called binSTEER.pkg is found the module.mk file will create an executable called STEER. Several *.pkg files can be placed in the same directory. The module.mk files is created on background of build/header.tpl and build/module.mk by variable substituion of variables @MODULE@ @PACKAGE@ and @TYPE@.
67 # The syntax for the pkg file is very simple. You specify the sources, headers and possibly extra include or link options. The *.pkg files is just inserted "as is" in the module.mk file, so normal Makefile syntax can be used. These variables can be specified: SRCS, FSRCS, CSRCS, HDRS, CHDRS, DHDR, EINCLUDE, ELIBS, ELIBSDIR, PACKFFLAGS, PACKCFLAGS, PACKCXXFLAGS. The first five is just the c++ sources, fortran sources, c sources, c++ headers and c headers. DHDR is the dictionary header and is the LinkDef file. EINCLUDE, ELIBS and ELIBSDIR is extra includedirs, libraries and library search paths. If for example a binary is to be linked against the variable ELIBSDIR would be set to lib/tgt_$ALICE_TARGET. Notice that -L and -l is not needed. If the PACKFFLAGS, PACKCFLAGS or PACKCXXFLAGS is not set it will be set to the default options (Set in config/Makefile.$ALICE_TARGET. For example on Linux GEANT321 has to be compiled without -O options, so a line like PACKFFLAGS := $(filter-out -O%,$(FFLAGS)) is needed.
72 # If alibtool is called with the depend command it will generate a dependecy file for the sourcefile given as second argument. This only goes for c++ and c files. If dependencies for fortran-fiels is needed, call alibtool with command dependF. The dependencies is made with rmkdepend.
77 # The same as depend, but for fortran files.
80 ###########################################################################
85 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'
89 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'
95 #This one gets all the library pkg files
96 tempo=`find ${module} -name "lib*.pkg" | sed -e "sQ${module}/libQQ" -e "sQ\.pkgQQ"`
98 echo "#**************************************************************************";
99 echo "#**** This file is automatically generated from the mkmodules script *****";
100 echo "#**** DO NOT EDIT!! *****";
101 echo "#**************************************************************************";
109 #This one gets all the binary(executable) pkg files
110 tempo=`find ${module} -name "bin*.pkg" | sed -e "sQ${module}/binQQ" -e "sQ\.pkgQQ"`
118 #Now make general bottom for every module (Clean and so on)
119 cat build/clean.tpl | sed -e "sQ\@MODULE@Q${module}Qg"
124 file=$module/$type$i.pkg
125 cat build/header.tpl | sed -e "sQ\@MODULE@Q${module}Qg" -e "sQ@PACKAGE@Q${package}Qg" -e "sQ\@TYPE@Q${type}Qg"
129 cat build/module.tpl | sed -e "sQ\@MODULE@Q${module}Qg" -e "sQ@PACKAGE@Q${package}Qg" -e "sQ\@TYPE@Q${type}Qg"