Gilles Gouaillardet 451b9dc467 ess: tear down pmix (if any) before oob		2016-10-13 14:08:02 +09:00
..
bindings	Fix the --tune problem by searching the argv for MCA params in advance of opal_init_util. Only search the first app_context as we historically have done - we can debate whether or not to search all app_contexts	2016-05-23 21:09:44 -07:00
etc	Purge whitespace from the repo	2015-06-23 20:59:57 -07:00
include	Bring the RML modifications across. This is the first step in a revamp of the ORTE messaging subsystem to support fabric-based communications during launch and wireup phases. When completed, the grpcomm and plm frameworks will each have their own "conduit" for communication - each conduit corresponds to a particular RML messaging transport. This can be the active OOB-based component, or a provider from within the RML/OFI component. Messages sent down the conduit will flow across the associated transport.	2016-10-11 16:01:02 -07:00
mca	ess: tear down pmix (if any) before oob	2016-10-13 14:08:02 +09:00
orted	Implement the backend support for process-generated event notification	2016-10-08 09:24:28 -07:00
runtime	Clean out old cruft from the ORCM project	2016-09-21 00:13:30 -07:00
test	Bring the RML modifications across. This is the first step in a revamp of the ORTE messaging subsystem to support fabric-based communications during launch and wireup phases. When completed, the grpcomm and plm frameworks will each have their own "conduit" for communication - each conduit corresponds to a particular RML messaging transport. This can be the active OOB-based component, or a provider from within the RML/OFI component. Messages sent down the conduit will flow across the associated transport.	2016-10-11 16:01:02 -07:00
tools	pkgconfig: define the pkgincludedir variable in *.pc files	2016-09-13 09:50:14 +09:00
util	Bring the RML modifications across. This is the first step in a revamp of the ORTE messaging subsystem to support fabric-based communications during launch and wireup phases. When completed, the grpcomm and plm frameworks will each have their own "conduit" for communication - each conduit corresponds to a particular RML messaging transport. This can be the active OOB-based component, or a provider from within the RML/OFI component. Messages sent down the conduit will flow across the associated transport.	2016-10-11 16:01:02 -07:00
common_sym_whitelist.txt	common syms: whitelist bison-generated common symbols	2016-01-16 03:53:14 -08:00
Doxyfile	Purge whitespace from the repo	2015-06-23 20:59:57 -07:00
Makefile.am	Purge whitespace from the repo	2015-06-23 20:59:57 -07:00