| 1 | # PLEASE adhere to the alphabetical ordering in this Makefile!
|
|---|
| 2 | # Also indentation by a single tab
|
|---|
| 3 |
|
|---|
| 4 | FRAGMENTATIONSETVALUESSOURCE = \
|
|---|
| 5 | Fragmentation/Summation/SetValues/Fragment.cpp \
|
|---|
| 6 | Fragmentation/Summation/SetValues/Histogram.cpp \
|
|---|
| 7 | Fragmentation/Summation/SetValues/IndexedVectors.cpp \
|
|---|
| 8 | Fragmentation/Summation/SetValues/SamplingGrid.cpp \
|
|---|
| 9 | Fragmentation/Summation/SetValues/SamplingGridProperties.cpp
|
|---|
| 10 |
|
|---|
| 11 | FRAGMENTATIONSETVALUESHEADER = \
|
|---|
| 12 | Fragmentation/Summation/SetValues/Fragment.hpp \
|
|---|
| 13 | Fragmentation/Summation/SetValues/Histogram.hpp \
|
|---|
| 14 | Fragmentation/Summation/SetValues/IndexedVectors.hpp \
|
|---|
| 15 | Fragmentation/Summation/SetValues/SamplingGrid.hpp \
|
|---|
| 16 | Fragmentation/Summation/SetValues/SamplingGrid_inline.hpp \
|
|---|
| 17 | Fragmentation/Summation/SetValues/SamplingGridProperties.hpp
|
|---|
| 18 |
|
|---|
| 19 | noinst_LTLIBRARIES += libMolecuilderFragmentationSetValues.la
|
|---|
| 20 | libMolecuilderFragmentationSetValues_la_includedir = $(includedir)/MoleCuilder/Fragmentation/Summation/SetValues/
|
|---|
| 21 | libMolecuilderFragmentationSetValues_la_CPPFLAGS = ${BOOST_CPPFLAGS} ${CodePatterns_CFLAGS}
|
|---|
| 22 | libMolecuilderFragmentationSetValues_la_LDFLAGS = -ldl ${BOOST_LDFLAGS}
|
|---|
| 23 | libMolecuilderFragmentationSetValues_la_LIBADD = \
|
|---|
| 24 | ${CodePatterns_LIBS}
|
|---|
| 25 |
|
|---|
| 26 | nobase_libMolecuilderFragmentationSetValues_la_include_HEADERS = ${FRAGMENTATIONSETVALUESHEADER}
|
|---|
| 27 |
|
|---|
| 28 | ## Define the source file list for the "libexample-@MOLECUILDER_API_VERSION@.la"
|
|---|
| 29 | ## target. Note that @MOLECUILDER_API_VERSION@ is not interpreted by Automake and
|
|---|
| 30 | ## will therefore be treated as if it were literally part of the target name,
|
|---|
| 31 | ## and the variable name derived from that.
|
|---|
| 32 | ## The file extension .cc is recognized by Automake, and makes it produce
|
|---|
| 33 | ## rules which invoke the C++ compiler to produce a libtool object file (.lo)
|
|---|
| 34 | ## from each source file. Note that it is not necessary to list header files
|
|---|
| 35 | ## which are already listed elsewhere in a _HEADERS variable assignment.
|
|---|
| 36 | libMolecuilderFragmentationSetValues_la_SOURCES = ${FRAGMENTATIONSETVALUESSOURCE}
|
|---|
| 37 |
|
|---|
| 38 | ## Instruct libtool to include ABI version information in the generated shared
|
|---|
| 39 | ## library file (.so). The library ABI version is defined in configure.ac, so
|
|---|
| 40 | ## that all version information is kept in one place.
|
|---|
| 41 | #libMolecuilderFragmentationSetValues_la_LDFLAGS += -version-info $(MOLECUILDER_SO_VERSION)
|
|---|
| 42 |
|
|---|
| 43 | ## The generated configuration header is installed in its own subdirectory of
|
|---|
| 44 | ## $(libdir). The reason for this is that the configuration information put
|
|---|
| 45 | ## into this header file describes the target platform the installed library
|
|---|
| 46 | ## has been built for. Thus the file must not be installed into a location
|
|---|
| 47 | ## intended for architecture-independent files, as defined by the Filesystem
|
|---|
| 48 | ## Hierarchy Standard (FHS).
|
|---|
| 49 | ## The nodist_ prefix instructs Automake to not generate rules for including
|
|---|
| 50 | ## the listed files in the distribution on 'make dist'. Files that are listed
|
|---|
| 51 | ## in _HEADERS variables are normally included in the distribution, but the
|
|---|
| 52 | ## configuration header file is generated at configure time and should not be
|
|---|
| 53 | ## shipped with the source tarball.
|
|---|
| 54 | #libMolecuilderFragmentationSetValues_libincludedir = $(libdir)/MoleCuilder/include
|
|---|
| 55 | #nodist_libMolecuilderFragmentationSetValues_libinclude_HEADERS = $(top_builddir)/libmolecuilder_config.h
|
|---|
| 56 |
|
|---|
| 57 | ## Install the generated pkg-config file (.pc) into the expected location for
|
|---|
| 58 | ## architecture-dependent package configuration information. Occasionally,
|
|---|
| 59 | ## pkg-config files are also used for architecture-independent data packages,
|
|---|
| 60 | ## in which case the correct install location would be $(datadir)/pkgconfig.
|
|---|
| 61 | #pkgconfigdir = $(libdir)/pkgconfig
|
|---|
| 62 | #pkgconfig_DATA = $(top_builddir)/MoleCuilder.pc
|
|---|
