1
1
openmpi/orte/tools/wrappers
Brian Barrett 581a4b0a4e A few cleanups to the wrapper compiler build system / man pages:
- Only install opal{cc,c++} and orte{cc,c++} if configured with
     --with-devel-headers.  Right now, they are always installed, but 
    there are no header files installed for either project, so there's
    really not much way for a user to actually compile an OPAL / ORTE
    application.

  - Drop support for opalCC and orteCC.  It's a pain to setup all the 
    symlinks (indeed, they are currently done wrong for opalCC) and 
    there's no history like there is for mpiCC.

  - Change what is currently opalcc.1 to opal_wrapper.1 and add some
    macros that get sed'ed so that the man pages appear to be 
    customized for the given command.  

  - Install the wrapper data files even if we compiled with 
    --disable-binaries.  This is for the use case of doing multi-lib
    builds, where one word size will only have the library built, but 
    we need both set of wrapper data files to piece together to 
    activate the multi-lib support in the wrapper compilers.

This commit was SVN r12192.
2006-10-19 18:34:17 +00:00
..
Makefile.am A few cleanups to the wrapper compiler build system / man pages: 2006-10-19 18:34:17 +00:00
ortec++-wrapper-data.txt.in Allow multilib capability based on compiler flags. See: 2006-10-15 21:21:08 +00:00
ortecc-wrapper-data.txt.in Allow multilib capability based on compiler flags. See: 2006-10-15 21:21:08 +00:00