openmpi/opal/mca/memcpy/configure.m4

dnl -*- shell-script -*-
dnl
dnl Copyright (c) 2004-2006 The University of Tennessee and The University
dnl                         of Tennessee Research Foundation.  All rights
dnl                         reserved.
dnl Copyright (c) 2004-2006 The Regents of the University of California.
dnl                         All rights reserved.
dnl $COPYRIGHT$
dnl 
dnl Additional copyrights may follow
dnl 
dnl $HEADER$
dnl

dnl we only want one
m4_define(MCA_memcpy_CONFIGURE_MODE, STOP_AT_FIRST)

AC_DEFUN([MCA_memcpy_CONFIG],[
        memcpy_base_include=

        # first, compile all the components
        MCA_CONFIGURE_FRAMEWORK($1, $2)

        # someone should have set this...
        if test "$memcpy_base_include" = "" ; then
            memcpy_base_include="base/memcpy_base_default.h"
        fi

        AC_DEFINE_UNQUOTED([MCA_memcpy_IMPLEMENTATION_HEADER],
                           ["opal/mca/memcpy/$memcpy_base_include"],
                           [Header to include for memcpy implementation])
])
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532. 2006-04-05 09:56:08 +04:00			`dnl -- shell-script --`
			`dnl`
			`dnl Copyright (c) 2004-2006 The University of Tennessee and The University`
			`dnl of Tennessee Research Foundation. All rights`
			`dnl reserved.`
* AC_CONFIG_LINKS has a minor problem in that it always uses ln -s, rather than $(LN_S). This causes problems with with Windows and probably elsewhere (re: #200). So use a slightly different trick to get the right header selected for the MEMCPY and TIMER components. * Using the same trick used to solve the AC_CONFIG_LINKS problem, stop using a separate header file for direct calling in the PML and MTL. This lets me remove some icky code in ompi_mca.m4 that was more fragile than I really liked. This commit was SVN r10841. 2006-07-16 08:23:52 +04:00			`dnl Copyright (c) 2004-2006 The Regents of the University of California.`
			`dnl All rights reserved.`
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532. 2006-04-05 09:56:08 +04:00			`dnl $COPYRIGHT$`
			`dnl`
			`dnl Additional copyrights may follow`
			`dnl`
			`dnl $HEADER$`
			`dnl`

* AC_CONFIG_LINKS has a minor problem in that it always uses ln -s, rather than $(LN_S). This causes problems with with Windows and probably elsewhere (re: #200). So use a slightly different trick to get the right header selected for the MEMCPY and TIMER components. * Using the same trick used to solve the AC_CONFIG_LINKS problem, stop using a separate header file for direct calling in the PML and MTL. This lets me remove some icky code in ompi_mca.m4 that was more fragile than I really liked. This commit was SVN r10841. 2006-07-16 08:23:52 +04:00			`dnl we only want one`
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532. 2006-04-05 09:56:08 +04:00			`m4_define(MCA_memcpy_CONFIGURE_MODE, STOP_AT_FIRST)`

			`AC_DEFUN([MCA_memcpy_CONFIG],[`
			`memcpy_base_include=`

			`# first, compile all the components`
			`MCA_CONFIGURE_FRAMEWORK($1, $2)`

			`# someone should have set this...`
			`if test "$memcpy_base_include" = "" ; then`
			`memcpy_base_include="base/memcpy_base_default.h"`
			`fi`

* AC_CONFIG_LINKS has a minor problem in that it always uses ln -s, rather than $(LN_S). This causes problems with with Windows and probably elsewhere (re: #200). So use a slightly different trick to get the right header selected for the MEMCPY and TIMER components. * Using the same trick used to solve the AC_CONFIG_LINKS problem, stop using a separate header file for direct calling in the PML and MTL. This lets me remove some icky code in ompi_mca.m4 that was more fragile than I really liked. This commit was SVN r10841. 2006-07-16 08:23:52 +04:00			`AC_DEFINE_UNQUOTED([MCA_memcpy_IMPLEMENTATION_HEADER],`
			`["opal/mca/memcpy/$memcpy_base_include"],`
			`[Header to include for memcpy implementation])`
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532. 2006-04-05 09:56:08 +04:00			`])`