Skip to content
Snippets Groups Projects
Commit 35f8fad5 authored by Thimo Neubauer's avatar Thimo Neubauer
Browse files

some fixes so that "make distcheck" generally works

[[Imported from SVN: r181]]
parent ba3c9e0f
No related branches found
No related tags found
No related merge requests found
......@@ -13,4 +13,5 @@ dune.pc
semantic.cache
configure.lineno
stamp-h1
dune-*.tar.gz
\ No newline at end of file
dune-*.tar.gz
dune-?.?
\ No newline at end of file
......@@ -9,3 +9,6 @@ SUBDIRS = common fem grid operator quadrature solver lib istl doc bin m4 am
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = dune.pc
# use configured compiler for "make distcheck"
# doxygen is difficult to convince to build in a special directory...
DISTCHECK_CONFIGURE_FLAGS = CXX="$(CXX)" CC="$(CC)" DOXYGEN="true"
#! /bin/bash
# $Id$
# Process this file with autoconf to produce a configure script.
AC_INIT(dune, 0.0, dune@hal.iwr.uni-heidelberg.de)
......@@ -49,23 +50,33 @@ AC_PROG_LN_S
if test x"$LN_S" == x"ln -s" ; then
# Symlinks possible!
# Note: we are currently in the build directory which may be != the
# source directory
# does a file already exist?
if test -e dune ; then
# exists: is a symlink?
if test -L dune ; then
if test -e dune/grid/common/grid.hh ; then
if test -r dune/grid/common/grid.hh ; then
# suppose that the link is ok and use it
AM_CPPFLAGS='-I$(top_srcdir)';
AM_CPPFLAGS='-I$(top_builddir)';
else
AC_MSG_ERROR([Symlink 'dune' exists but appears to be wrong! Please remove it manually])
fi
fi
else
echo Creating dune-symlink...
# set symlink
ln -s . dune ;
# set symlink in build directory to sources
ln -s $srcdir dune
# sanity check
if test -r dune/grid/common/grid.hh ; then
AM_CPPFLAGS='-I$(top_builddir)';
else
AC_MSG_ERROR([Sanity check for symlink failed! Please send a bugreport to dune@hal.iwr.uni-heidelberg.de])
fi
# set proper include-path
AM_CPPFLAGS='-I$(top_srcdir)';
AM_CPPFLAGS='-I$(top_builddir)';
fi
else
# no symlinks possible... check name of directory
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment