opm-core/configure.ac

#                                               -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.

AC_PREREQ([2.59])
AC_INIT([OPM Core Library], [0.1], [atgeirr@sintef.no],dnl
        [opmcore], [https://public.ict.sintef.no/opm/hg/opmcore])
AM_INIT_AUTOMAKE([-Wall -Werror foreign subdir-objects])

m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])

AC_CONFIG_MACRO_DIR([m4])
AC_CONFIG_SRCDIR([opm/core/grid.h])
AC_CONFIG_HEADERS([config.h])

# Checks for programs.
AC_PROG_CC
AM_PROG_CC_C_O

m4_ifdef([LT_INIT],
         [LT_INIT[]dnl
          LT_LANG([C++])dnl
          LT_LANG([Fortran 77])dnl
          LT_LANG([Fortran])dnl
         ],dnl
         [AC_PROG_LIBTOOL[]dnl
          AC_PROG_CXX[]dnl
          AC_PROG_F77[]dnl
          AC_PROG_FC[]dnl
         ])[]dnl

OPM_CORE_CHECKS

OPM_DYNLINK_BOOST_TEST

AC_CONFIG_FILES([
 Makefile
 tests/Makefile
 examples/Makefile
 tutorials/Makefile
])

AC_OUTPUT
Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00			`# -- Autoconf --`
			`# Process this file with autoconf to produce a configure script.`

Now configuration succeeds for CentOS 5.7. 2011-12-12 14:57:09 +01:00			`AC_PREREQ([2.59])`
Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00			`AC_INIT([OPM Core Library], [0.1], [atgeirr@sintef.no],dnl`
			`[opmcore], [https://public.ict.sintef.no/opm/hg/opmcore])`
			`AM_INIT_AUTOMAKE([-Wall -Werror foreign subdir-objects])`

			`m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])`

			`AC_CONFIG_MACRO_DIR([m4])`
Updated for changed paths. 2011-12-12 11:29:14 +01:00			`AC_CONFIG_SRCDIR([opm/core/grid.h])`
Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00			`AC_CONFIG_HEADERS([config.h])`

			`# Checks for programs.`
			`AC_PROG_CC`
AM_PROG_CC_C_O needed because of subdir objects. 2012-01-06 11:22:35 +01:00			`AM_PROG_CC_C_O`
Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00
Revamp Fortran support in preparation of enabling Notay's AGMG solver. Specifically: - Enable C++, Fortran 77 and Fortran (95+) through Libtool's LT_LANG if available and through the traditional AC_PROG_* macros if not. This configuration is compatible with the versions of Libtool easily available for testing. For whatever reason--possibly a programming error in Libtool proper--invoking the AC_PROG_F* macros either directly or through AC_REQUIRE following an LT_INIT invocation leads to various ``expanded before required'' warnings. Searching the Autotools mailing lists does suggest that the interaction of C++, Fortran and Libtool is traditionally somewhat unstable but has improved in very recent editions of Autoconf and Libtool. - Re-factor the LAPACK support out to a custom macro, OPM_LAPACK, and invoke it from configure.ac. 2012-06-05 18:40:36 +02:00			`m4_ifdef([LT_INIT],`
			`[LT_INIT[]dnl`
			`LT_LANG([C++])dnl`
			`LT_LANG([Fortran 77])dnl`
			`LT_LANG([Fortran])dnl`
			`],dnl`
			`[AC_PROG_LIBTOOL[]dnl`
			`AC_PROG_CXX[]dnl`
			`AC_PROG_F77[]dnl`
			`AC_PROG_FC[]dnl`
			`])[]dnl`
Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00
opm-core: make it a usable in conjunction wit dunecontrol This allows projects which use the DUNE build system and want to use OPM-Core to specify a dependency in their dune.module file. (i.e. they don't have to worry about compiler and linker flags anymore.) opm-core can still be used without having DUNE installed, though. This means that for users which do not need/want a dependency on DUNE, nothing changes. v2: avoid naming conflict of the AX_BOOST_BASE macro with dune-common by renaming it to OPM_BOOST_BASE. v3: make the library detection work nicely v4: Use AX_BOOST_BASE M4 macro from opm-core instead from dune-common as base for OPM_BOOST_BASE to get rid of a few bugs, reworded commit message. Thanks to Bård Skaflestad for the review. 2012-06-14 18:13:56 +02:00			`OPM_CORE_CHECKS`
Initial version of automatic checking for dune-istl in build system. 2012-04-13 15:35:19 +02:00
Add AC macro to determine how to link Boost.Test Details: Test suites based on Boost.Test must know how to include the library support code into the executables. If the Boost.Test library is dynamically linked, then test suites must define the pre-processor symbol "BOOST_TEST_DYN_LINK". Otherwise, this symbol must not be defined. Resolution: Introduce a new Autoconf macro, OPM_DYNLINK_BOOST_TEST, that defines a secondary symbol--HAVE_DYNAMIC_BOOST_TEST--if the local computer system uses dynamic linking. Test suites (e.g., tests/param_test.cpp) may then inspect this symbol to determine whether or not to #define BOOST_TEST_DYN_LINK. Call the macro from "configure.ac". Suggested by: Joakim Hove 2012-06-27 16:25:46 +02:00			`OPM_DYNLINK_BOOST_TEST`

Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00			`AC_CONFIG_FILES([`
			`Makefile`
			`tests/Makefile`
			`examples/Makefile`
Fixed configure.ac file to take into account tutorials 2012-04-10 17:46:52 +02:00			`tutorials/Makefile`
Complete cset ad3d926031e7. 2011-12-08 14:49:09 +01:00			`])`

			`AC_OUTPUT`