--- PamCut/makefile 2009/08/26 16:34:13 1.5 +++ PamCut/makefile 2010/03/24 08:11:25 1.9 @@ -26,8 +26,13 @@ # "#ifdef DEBUGPAMCUT" and "#endif"). Note that if you # use debug instructions also in the .h code (headers) you will also have to add -DDEBUGPAMCUT # to the compiler options for the main analysis program. +# 3) Since this is a general compiler flag it can also be used, eg., to set the -m32 flag OPTIMIZE = -g3 #-DDEBUGPAMCUT +# Linker flags +# The flags defined here will be directly inserted into the linker invocation. Place here the +# -m32 flag, for example. +LINKERFLAGS = # Library flags # Pamela software is modular, so some libraries may not be available in some istallations. @@ -35,8 +40,18 @@ # PamCut software which make use of unavailable libraries. Remember to place # the code to be excluded between proper preprocessor directives. See the documentation or the cut # TofNucleiZCut for an example. +# Since PamCut headers may refer to the optional libraries, it's important to define the same +# flags when compiling the analysis code. Otherwise, analysis code will include PamCut headers which, +# if no exclusion flag is set, will try to include optional software headers. +# Conversely, if you use optional libraries remember to tell it to the linker. +# +# Excluded cuts and actions: +# DNO_CALONUCLEI: CaloNucleiZCut +# NO_TRKNUCLEI: TrkNucleiZCut +# NO_TOFNUCLEI: TofNucleiZCut +# NO_CALOPRESAMPLER: ReprocessCaloAction -EXCLUSIONFLAGS = -DNO_CALONUCLEI -DNO_TRKNUCLEI #-DNO_TOFNUCLEI -DNO_CALONUCLEI -DNO_TRKNUCLEI +EXCLUSIONFLAGS = -DNO_CALONUCLEI -DNO_TRKNUCLEI -DNO_TOFNUCLEI #-DNO_CALOPRESAMPLER # Put below the files on which every .cpp must depend on, ie., those files that, # if modified, will trigger a complete recompilation of the project. @@ -73,7 +88,7 @@ libPamCut.so: $(OBJS) $(USER_OBJS) @echo 'Building target: $@' @echo 'Invoking: GCC C++ Linker' - $(C++) -shared -o"libPamCut.so" $(OBJS) + $(C++) -shared $(LINKERFLAGS) -o"libPamCut.so" $(OBJS) @echo 'Finished building target: $@' @echo ' '