| 1 | # PLEASE adhere to the alphabetical ordering in this Makefile!
|
|---|
| 2 | # Also indentation by a single tab
|
|---|
| 3 |
|
|---|
| 4 | PYTHONSOURCE = \
|
|---|
| 5 | Python/exit.cpp \
|
|---|
| 6 | Python/export_numpy.cpp \
|
|---|
| 7 | Python/getBoundingBox.cpp \
|
|---|
| 8 | Python/getDomainVolume.cpp \
|
|---|
| 9 | Python/getGraph6String.cpp \
|
|---|
| 10 | Python/getSelectedAtomCount.cpp \
|
|---|
| 11 | Python/getSelectedAtomElements.cpp \
|
|---|
| 12 | Python/getSelectedAtomIds.cpp \
|
|---|
| 13 | Python/getSelectedAtomPositions.cpp \
|
|---|
| 14 | Python/getSelectedMolarMass.cpp \
|
|---|
| 15 | Python/PythonScripting.cpp \
|
|---|
| 16 | Python/reinit.cpp \
|
|---|
| 17 | Python/wait.cpp
|
|---|
| 18 |
|
|---|
| 19 | PYTHONHEADER = \
|
|---|
| 20 | Python/modules.hpp \
|
|---|
| 21 | Python/PythonScripting_impl.hpp \
|
|---|
| 22 | Python/PythonScripting.hpp
|
|---|
| 23 |
|
|---|
| 24 | pkgpython_PYTHON = \
|
|---|
| 25 | Python/capture_c_contextmanager.py
|
|---|
| 26 |
|
|---|
| 27 | noinst_LTLIBRARIES += libMolecuilderPython.la
|
|---|
| 28 | libMolecuilderPython_la_includedir = $(includedir)/MoleCuilder/
|
|---|
| 29 | libMolecuilderPython_la_CPPFLAGS = $(AM_CPPFLAGS) $(BOOST_PYTHON_CPPFLAGS)
|
|---|
| 30 | libMolecuilderPython_la_LDFLAGS = $(AM_LDFLAGS) $(BOOST_NUMPY_LDFLAGS) $(BOOST_PYTHON_LDFLAGS)
|
|---|
| 31 | libMolecuilderPython_la_LIBADD = \
|
|---|
| 32 | $(BOOST_NUMPY_LIBS) \
|
|---|
| 33 | $(BOOST_PYTHON_LIBS) \
|
|---|
| 34 | $(BOOST_PYTHON_LIB) \
|
|---|
| 35 | ${CodePatterns_LIBS}
|
|---|
| 36 |
|
|---|
| 37 | nobase_libMolecuilderPython_la_include_HEADERS = ${PYTHONHEADER}
|
|---|
| 38 |
|
|---|
| 39 | ## Define the source file list for the "libexample-@MOLECUILDER_API_VERSION@.la"
|
|---|
| 40 | ## target. Note that @MOLECUILDER_API_VERSION@ is not interpreted by Automake and
|
|---|
| 41 | ## will therefore be treated as if it were literally part of the target name,
|
|---|
| 42 | ## and the variable name derived from that.
|
|---|
| 43 | ## The file extension .cc is recognized by Automake, and makes it produce
|
|---|
| 44 | ## rules which invoke the C++ compiler to produce a libtool object file (.lo)
|
|---|
| 45 | ## from each source file. Note that it is not necessary to list header files
|
|---|
| 46 | ## which are already listed elsewhere in a _HEADERS variable assignment.
|
|---|
| 47 | libMolecuilderPython_la_SOURCES = ${PYTHONSOURCE}
|
|---|
| 48 |
|
|---|
| 49 | ## Instruct libtool to include ABI version information in the generated shared
|
|---|
| 50 | ## library file (.so). The library ABI version is defined in configure.ac, so
|
|---|
| 51 | ## that all version information is kept in one place.
|
|---|
| 52 | #libMolecuilderPython_la_LDFLAGS = -version-info $(MOLECUILDER_SO_VERSION)
|
|---|
| 53 |
|
|---|
| 54 | ## The generated configuration header is installed in its own subdirectory of
|
|---|
| 55 | ## $(libdir). The reason for this is that the configuration information put
|
|---|
| 56 | ## into this header file describes the target platform the installed library
|
|---|
| 57 | ## has been built for. Thus the file must not be installed into a location
|
|---|
| 58 | ## intended for architecture-independent files, as defined by the Filesystem
|
|---|
| 59 | ## Hierarchy Standard (FHS).
|
|---|
| 60 | ## The nodist_ prefix instructs Automake to not generate rules for including
|
|---|
| 61 | ## the listed files in the distribution on 'make dist'. Files that are listed
|
|---|
| 62 | ## in _HEADERS variables are normally included in the distribution, but the
|
|---|
| 63 | ## configuration header file is generated at configure time and should not be
|
|---|
| 64 | ## shipped with the source tarball.
|
|---|
| 65 | #libMolecuilderPython_libincludedir = $(libdir)/MoleCuilder/include
|
|---|
| 66 | #nodist_libMolecuilderPython_libinclude_HEADERS = $(top_builddir)/libmolecuilder_config.h
|
|---|
| 67 |
|
|---|
| 68 | ## Install the generated pkg-config file (.pc) into the expected location for
|
|---|
| 69 | ## architecture-dependent package configuration information. Occasionally,
|
|---|
| 70 | ## pkg-config files are also used for architecture-independent data packages,
|
|---|
| 71 | ## in which case the correct install location would be $(datadir)/pkgconfig.
|
|---|
| 72 | #pkgconfigdir = $(libdir)/pkgconfig
|
|---|
| 73 | #pkgconfig_DATA = $(top_builddir)/MoleCuilder.pc
|
|---|
