Makefile.am

AUTOMAKE_OPTIONS = no-dependencies
ACLOCAL_AMFLAGS = -I m4

# todo: we don't want std=c99 in there, but AX_MPI changes *CC*, not CFLAGS!
# so we don't know the real option for c99, need a workaround.
# todo: grumble number 2: sometimes we have code that needs *both* MPI *and*
# Python.  For now, we just throw PYTHON_CPPFLAGS in here, but this solution
# sucks because in general we might want code which is just python code, or
# code which is just MPI code, and the two libraries' flags may interact in a
# bad way.  Meh.
.mpic.lo:
	$(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) \
    --mode=compile $(MPICC) -x c $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) \
    @PYTHON_CPPFLAGS@ \
    $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -std=c99 -c -o $@ $<

LIB_LTLIBRARIES = libsitu.la
libsitu_la_SOURCES = \
  $(top_srcdir)/debug.c \
  $(top_srcdir)/fproc.c \
  $(top_srcdir)/h5.c \
  $(top_srcdir)/posix.c \
  $(top_srcdir)/simplesitu.c
libsitu_la_LIBADD = -ldl -lrt @LTLIBOBJS@

bin_PROGRAMS = situ
situ_SOURCES = forkenv.c evfork.c

# set it to an empty value, because automake complains if one tries to '+=' on
# a variable which wasn't yet defined.
pkglib_LTLIBRARIES =

include processors/hello/mk.inc
include processors/minmax/mk.inc
include processors/netz/mk.inc
include processors/nositu/mk.inc
include processors/python/mk.inc