Ralph Castain 63f619f871 Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

..

generic_wrapper.1in

wrappers: update URLs for GitHub

2014-10-01 14:37:17 -07:00

help-opal-wrapper.txt

opal wrappers: Remove unused help message; add missing help message

2014-04-07 15:35:31 +00:00

Makefile.am

Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

opal_wrapper.1in

The final step of the RFC: convert the <foo>libdir and friends to fit their respective code areas, and equate them all at the top. Note that we can't entirely separate things as the opal_install_dirs framework can't handle separated locations for the various trees.

2014-05-08 02:01:35 +00:00

opal_wrapper.c

The final step of the RFC: convert the <foo>libdir and friends to fit their respective code areas, and equate them all at the top. Note that we can't entirely separate things as the opal_install_dirs framework can't handle separated locations for the various trees.

2014-05-08 02:01:35 +00:00

opal.pc.in

Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

opalc++-wrapper-data.txt.in

Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

opalcc-wrapper-data.txt.in

Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00