1
1
openmpi/ompi/mca/op/example/configure.m4
Ralph Castain 40a2bfa238 WARNING: Work on the temp branch being merged here encountered problems with bugs in subversion. Considerable effort has gone into validating the branch. However, not all conditions can be checked, so users are cautioned that it may be advisable to not update from the trunk for a few days to allow MTT to identify platform-specific issues.
This merges the branch containing the revamped build system based around converting autogen from a bash script to a Perl program. Jeff has provided emails explaining the features contained in the change.

Please note that configure requirements on components HAVE CHANGED. For example. a configure.params file is no longer required in each component directory. See Jeff's emails for an explanation.

This commit was SVN r23764.
2010-09-17 23:04:06 +00:00

72 строки
3.1 KiB
Bash

# -*- shell-script -*-
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
# University Research and Technology
# Corporation. All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
# of Tennessee Research Foundation. All rights
# reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
# University of Stuttgart. All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
# All rights reserved.
# Copyright (c) 2008-2010 Cisco Systems, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# Example op component configure.m4 file. This file is slurped in by
# Open MPI's autogen.pl to be part of the top-level configure script.
# This script must define (via AC_DEFUN) an m4 macro named
# MCA_<framework>_<component>_CONFIG that executes either $1 if the
# component wants to build itself, or $2 if the component does not
# want to build itself.
# Do *NOT* invoke AC_MSG_ERROR, or any other macro that will abort
# configure, except upon catastrophic error. For example, it *is* a
# catastropic error if the user specifically requested your component
# but it cannot be built. If it *not* a catastropic error if your
# component cannot be built (but was not specifically requested).
# See https://svn.open-mpi.org/trac/ompi/wiki/devel/CreateComponent
# for more details on how to make Open MPI components.
# MCA_op_example_CONFIG([action-if-found], [action-if-not-found])
# -----------------------------------------------------------
AC_DEFUN([MCA_ompi_op_example_CONFIG],[
AC_CONFIG_FILES([ompi/mca/op/example/Makefile])
# Add checks here for any necessary header files and/or libraries
# that must be present to compile your component.
# This example performs a fairly simple test (checking for the
# "struct sockaddr_in" C type), just for the sake of showing you
# one test and executing either $1 or $2, depending on the output
# of the test.
# check for sockaddr_in (a good sign we have TCP)
AC_CHECK_TYPES([struct sockaddr_in],
[$1],
[$2],
[AC_INCLUDES_DEFAULT
#ifdef HAVE_NETINET_IN_H
#include <netinet/in.h>
#endif])
# Let's pretend that we found version A.B.C of the "libfoo"
# support library that is necessary to compile/link this
# component. We'll AC_DEFINE the A, B, and C values so that they
# can be printed as information MCA parameters via ompi_info. See
# op_example_component.c to see how these values are used.
AC_DEFINE_UNQUOTED(OP_EXAMPLE_LIBFOO_VERSION_MAJOR, ["17"],
[Major version number of the "libfoo" library])
AC_DEFINE_UNQUOTED(OP_EXAMPLE_LIBFOO_VERSION_MINOR, ["38"],
[Minor version number of the "libfoo" library])
AC_DEFINE_UNQUOTED(OP_EXAMPLE_LIBFOO_VERSION_RELEASE, ["4"],
[Release version number of the "libfoo" library])
])dnl