openmpi

Ralph Castain 2b7a3ae601 Per RFC, continue pecking away at the build system renaming OMPI_CONFIG_SUBDIR -> OPAL_CONFIG_SUBDIR OMPI_CONFIG_SUBDIR_ARGS -> OPAL_CONFIG_SUBDIR_ARGS This commit was SVN r31647.		2014-05-06 16:27:38 +00:00
..
libompitrace	MPI-3.0: update C bindings with const and consistent use of [] for	2013-09-26 21:56:20 +00:00
vt	Per RFC, continue pecking away at the build system renaming	2014-05-06 16:27:38 +00:00
README.txt	Update the text; it was left over from autogen.sh days (i.e., it had	2012-01-26 13:11:36 +00:00

README.txt

This is the OMPI contrib system.  It is (far) less functional and
flexible than the OMPI MCA framework/component system.

Each contrib package must have a configure.m4.  It may optionally also
have an autogen.subdirs file.

If it has a configure.m4 file, it must specify its own relevant files
to AC_CONFIG_FILES to create during AC_OUTPUT -- just like MCA
components (at a minimum, usually its own Makefile).  The configure.m4
file will be slurped up into the main configure script, just like
other MCA components.  Note that there is currently no "no configure"
option for contrib packages -- you *must* have a configure.m4 (even if
all it does it call $1).  Feel free to fix this situation if you want
-- it probably won't not be too difficult to extend autogen.pl to
support this scenario, similar to how it is done for MCA components.
:-)

If it has an autogen.subdirs file, then it needs to be a subdirectory
that is autogen-able (see the vt project for an example).