| 1 | # PLEASE adhere to the alphabetical ordering in this Makefile!
|
|---|
| 2 | # Also indentation by a single tab
|
|---|
| 3 |
|
|---|
| 4 |
|
|---|
| 5 | PARAMETERSOURCE = \
|
|---|
| 6 | Parameters/Validators/Specific/BoxLengthValidator.cpp
|
|---|
| 7 |
|
|---|
| 8 | PARAMETERHEADER = \
|
|---|
| 9 | Parameters/Parameter.hpp \
|
|---|
| 10 | Parameters/Parameter_impl.hpp \
|
|---|
| 11 | Parameters/ParameterAsString.hpp \
|
|---|
| 12 | Parameters/ParameterInterface.hpp \
|
|---|
| 13 | Parameters/Validators/DiscreteValidator.hpp \
|
|---|
| 14 | Parameters/Validators/DiscreteValidator_impl.hpp \
|
|---|
| 15 | Parameters/Validators/Ops_Validator.hpp \
|
|---|
| 16 | Parameters/Validators/Ops_Validator_impl.hpp \
|
|---|
| 17 | Parameters/Validators/RangeValidator.hpp \
|
|---|
| 18 | Parameters/Validators/RangeValidator_impl.hpp \
|
|---|
| 19 | Parameters/Validators/STLVectorValidator.hpp \
|
|---|
| 20 | Parameters/Validators/Validator.hpp \
|
|---|
| 21 | Parameters/Validators/Specific/BoxLengthValidator.hpp \
|
|---|
| 22 | Parameters/Validators/Specific/ElementValidator.hpp \
|
|---|
| 23 | Parameters/Validators/Specific/FilePresentValidator.hpp \
|
|---|
| 24 | Parameters/Value.hpp \
|
|---|
| 25 | Parameters/Value_impl.hpp \
|
|---|
| 26 | Parameters/ValueAsString.hpp \
|
|---|
| 27 | Parameters/ValueInterface.hpp
|
|---|
| 28 |
|
|---|
| 29 | noinst_LTLIBRARIES += libMolecuilderParameters.la
|
|---|
| 30 | libMolecuilderParameters_la_includedir = $(includedir)/MoleCuilder/Parameters/
|
|---|
| 31 |
|
|---|
| 32 | nobase_libMolecuilderParameters_la_include_HEADERS = ${PARAMETERHEADER}
|
|---|
| 33 |
|
|---|
| 34 | ## Define the source file list for the "libexample-@MOLECUILDER_API_VERSION@.la"
|
|---|
| 35 | ## target. Note that @MOLECUILDER_API_VERSION@ is not interpreted by Automake and
|
|---|
| 36 | ## will therefore be treated as if it were literally part of the target name,
|
|---|
| 37 | ## and the variable name derived from that.
|
|---|
| 38 | ## The file extension .cc is recognized by Automake, and makes it produce
|
|---|
| 39 | ## rules which invoke the C++ compiler to produce a libtool object file (.lo)
|
|---|
| 40 | ## from each source file. Note that it is not necessary to list header files
|
|---|
| 41 | ## which are already listed elsewhere in a _HEADERS variable assignment.
|
|---|
| 42 | libMolecuilderParameters_la_SOURCES = ${PARAMETERSOURCE}
|
|---|
| 43 |
|
|---|
| 44 | ## Instruct libtool to include ABI version information in the generated shared
|
|---|
| 45 | ## library file (.so). The library ABI version is defined in configure.ac, so
|
|---|
| 46 | ## that all version information is kept in one place.
|
|---|
| 47 | #libMolecuilderParameters_la_LDFLAGS = -version-info $(MOLECUILDER_SO_VERSION)
|
|---|
| 48 |
|
|---|
| 49 | ## The generated configuration header is installed in its own subdirectory of
|
|---|
| 50 | ## $(libdir). The reason for this is that the configuration information put
|
|---|
| 51 | ## into this header file describes the target platform the installed library
|
|---|
| 52 | ## has been built for. Thus the file must not be installed into a location
|
|---|
| 53 | ## intended for architecture-independent files, as defined by the Filesystem
|
|---|
| 54 | ## Hierarchy Standard (FHS).
|
|---|
| 55 | ## The nodist_ prefix instructs Automake to not generate rules for including
|
|---|
| 56 | ## the listed files in the distribution on 'make dist'. Files that are listed
|
|---|
| 57 | ## in _HEADERS variables are normally included in the distribution, but the
|
|---|
| 58 | ## configuration header file is generated at configure time and should not be
|
|---|
| 59 | ## shipped with the source tarball.
|
|---|
| 60 | #libMolecuilderParameters_libincludedir = $(libdir)/MoleCuilder/include
|
|---|
| 61 | #nodist_libMolecuilderParameters_libinclude_HEADERS = $(top_builddir)/libmolecuilder_config.h
|
|---|
| 62 |
|
|---|
| 63 | ## Install the generated pkg-config file (.pc) into the expected location for
|
|---|
| 64 | ## architecture-dependent package configuration information. Occasionally,
|
|---|
| 65 | ## pkg-config files are also used for architecture-independent data packages,
|
|---|
| 66 | ## in which case the correct install location would be $(datadir)/pkgconfig.
|
|---|
| 67 | #pkgconfigdir = $(libdir)/pkgconfig
|
|---|
| 68 | #pkgconfig_DATA = $(top_builddir)/MoleCuilder.pc
|
|---|
