ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
477828159e
openmpi/orte/tools/wrappers/Makefile.am

59 строки
1.9 KiB
Makefile
Исходник Обычный вид История

* Merge of wrapper compiler updates from the bwb-wrapper-fix branch (r8690 - r8698), with changes below: - Split wrapper flags into those required for each of the three projects, and cleaned up some cruft (including the LIBMPI_EXTRA_*FLAGS) through- out the build system - Added opal_init_util and opal_finalize_util to allow init / cleanup of all the opal code that doesn't require the MCA system - Create standalone key=value file parser, based on the one that used to be in the mca param parser, so that it can be shared in multiple places - Add wrapper datafiles for opal, orte, and ompi wrappers, and add wrapper compiler with support for all the old features This commit was SVN r8699. The following SVN revisions from the original message are invalid or inconsistent and therefore were not cross-referenced: r8690 r8698
2006-01-16 04:48:03 +03:00
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
# University Research and Technology
# Corporation. All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
# of Tennessee Research Foundation. All rights
# reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
# University of Stuttgart. All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
# All rights reserved.
Add man page for wrapper compilers. Fixes trac:358. This commit was SVN r11773. The following Trac tickets were found above: Ticket 358 --> https://svn.open-mpi.org/trac/ompi/ticket/358
2006-09-25 18:11:21 +04:00
# Copyright (c) 2006 Cisco Systems, Inc. All rights reserved.
* Merge of wrapper compiler updates from the bwb-wrapper-fix branch (r8690 - r8698), with changes below: - Split wrapper flags into those required for each of the three projects, and cleaned up some cruft (including the LIBMPI_EXTRA_*FLAGS) through- out the build system - Added opal_init_util and opal_finalize_util to allow init / cleanup of all the opal code that doesn't require the MCA system - Create standalone key=value file parser, based on the one that used to be in the mca param parser, so that it can be shared in multiple places - Add wrapper datafiles for opal, orte, and ompi wrappers, and add wrapper compiler with support for all the old features This commit was SVN r8699. The following SVN revisions from the original message are invalid or inconsistent and therefore were not cross-referenced: r8690 r8698
2006-01-16 04:48:03 +03:00
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
Grrr... Forgot that EXTRA_DIST and man_MANS are not set to include all the possible things contained in the conditional like other rules are (for example, a SOURCES rule in a conditional automatically has its files added to the dist rules, even if that conditional isn't tru when make dist occurs). So the man files weren't in the tarball. Put the EXTRA_DIST with the files explicitly listed outside any conditionals so the man pages always end up in the tarball. This commit was SVN r12220.
2006-10-20 18:15:38 +04:00
EXTRA_DIST = \
ortecc.1 \
ortec++.1
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 22:34:17 +04:00
if WANT_INSTALL_HEADERS
Add a feature to the build system that Terry from Sun and I talked about in San Jose. Allow the configure option --disable-binaries to build OMPI, but not build or install the support binaries (so basically, just build the libraries). This commit was SVN r9777.
2006-04-29 06:16:41 +04:00
* Merge of wrapper compiler updates from the bwb-wrapper-fix branch (r8690 - r8698), with changes below: - Split wrapper flags into those required for each of the three projects, and cleaned up some cruft (including the LIBMPI_EXTRA_*FLAGS) through- out the build system - Added opal_init_util and opal_finalize_util to allow init / cleanup of all the opal code that doesn't require the MCA system - Create standalone key=value file parser, based on the one that used to be in the mca param parser, so that it can be shared in multiple places - Add wrapper datafiles for opal, orte, and ompi wrappers, and add wrapper compiler with support for all the old features This commit was SVN r8699. The following SVN revisions from the original message are invalid or inconsistent and therefore were not cross-referenced: r8690 r8698
2006-01-16 04:48:03 +03:00
nodist_pkgdata_DATA = \
ortecc-wrapper-data.txt \
ortec++-wrapper-data.txt
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 22:34:17 +04:00
if OMPI_INSTALL_BINARIES
Move the man page installs to install-data-hook. Putting them in install-exec-hook is not only wrong, it can cause ordering issues such as trying to put sym links to man pages in directories that do not yet exist. This commit was SVN r11893.
2006-09-29 18:34:39 +04:00
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 22:34:17 +04:00
man_MANS = \
ortecc.1 \
ortec++.1
* Merge of wrapper compiler updates from the bwb-wrapper-fix branch (r8690 - r8698), with changes below: - Split wrapper flags into those required for each of the three projects, and cleaned up some cruft (including the LIBMPI_EXTRA_*FLAGS) through- out the build system - Added opal_init_util and opal_finalize_util to allow init / cleanup of all the opal code that doesn't require the MCA system - Create standalone key=value file parser, based on the one that used to be in the mca param parser, so that it can be shared in multiple places - Add wrapper datafiles for opal, orte, and ompi wrappers, and add wrapper compiler with support for all the old features This commit was SVN r8699. The following SVN revisions from the original message are invalid or inconsistent and therefore were not cross-referenced: r8690 r8698
2006-01-16 04:48:03 +03:00
install-exec-hook:
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 22:34:17 +04:00
test -z "$(bindir)" || $(mkdir_p) "$(DESTDIR)$(bindir)"
* Merge of wrapper compiler updates from the bwb-wrapper-fix branch (r8690 - r8698), with changes below: - Split wrapper flags into those required for each of the three projects, and cleaned up some cruft (including the LIBMPI_EXTRA_*FLAGS) through- out the build system - Added opal_init_util and opal_finalize_util to allow init / cleanup of all the opal code that doesn't require the MCA system - Create standalone key=value file parser, based on the one that used to be in the mca param parser, so that it can be shared in multiple places - Add wrapper datafiles for opal, orte, and ompi wrappers, and add wrapper compiler with support for all the old features This commit was SVN r8699. The following SVN revisions from the original message are invalid or inconsistent and therefore were not cross-referenced: r8690 r8698
2006-01-16 04:48:03 +03:00
(cd $(DESTDIR)$(bindir); rm -f ortecc$(EXEEXT); $(LN_S) opal_wrapper ortecc)
(cd $(DESTDIR)$(bindir); rm -f ortec++$(EXEEXT); $(LN_S) opal_wrapper ortec++)
Move the man page installs to install-data-hook. Putting them in install-exec-hook is not only wrong, it can cause ordering issues such as trying to put sym links to man pages in directories that do not yet exist. This commit was SVN r11893.
2006-09-29 18:34:39 +04:00
* Merge of wrapper compiler updates from the bwb-wrapper-fix branch (r8690 - r8698), with changes below: - Split wrapper flags into those required for each of the three projects, and cleaned up some cruft (including the LIBMPI_EXTRA_*FLAGS) through- out the build system - Added opal_init_util and opal_finalize_util to allow init / cleanup of all the opal code that doesn't require the MCA system - Create standalone key=value file parser, based on the one that used to be in the mca param parser, so that it can be shared in multiple places - Add wrapper datafiles for opal, orte, and ompi wrappers, and add wrapper compiler with support for all the old features This commit was SVN r8699. The following SVN revisions from the original message are invalid or inconsistent and therefore were not cross-referenced: r8690 r8698
2006-01-16 04:48:03 +03:00
uninstall-local:
rm -f $(DESTDIR)$(bindir)/ortecc$(EXEEXT) \
$(DESTDIR)$(bindir)/ortec++$(EXEEXT)
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 22:34:17 +04:00
endif # OMPI_INSTALL_BINARIES
endif # WANT_INSTALL_HEADERS
- Clean up wrapper compiler man pages during maintainer-clean, since they might require special tools (not sure if sed with multiple -e arguments is totally portable) - ignore the opalcc.1 man page. Couldn't do this in the previous man page commit (r12192) because I was removing opalcc.1 in that commit. This commit was SVN r12194. The following SVN revision numbers were found above: r12192 --> open-mpi/ompi@581a4b0a4ebb9ce8d9732bfb17b5c94d42e71601
2006-10-20 00:14:40 +04:00
maintainer-clean-local:
rm -f ortecc.1 ortec++.1
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 22:34:17 +04:00
ortecc.1: $(top_srcdir)/opal/tools/wrappers/opal_wrapper.1
rm -f ortecc.1
sed -e 's/@COMMAND@/ortecc/g' -e 's/@PROJECT@/OpenRTE/g' -e 's/@PROJECT_SHORT@/ORTE/g' -e 's/@LANGUAGE@/C/g' < $(top_srcdir)/opal/tools/wrappers/opal_wrapper.1 > ortecc.1
Add a feature to the build system that Terry from Sun and I talked about in San Jose. Allow the configure option --disable-binaries to build OMPI, but not build or install the support binaries (so basically, just build the libraries). This commit was SVN r9777.
2006-04-29 06:16:41 +04:00
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 22:34:17 +04:00
ortec++.1: $(top_srcdir)/opal/tools/wrappers/opal_wrapper.1
rm -f ortec++.1
sed -e 's/@COMMAND@/ortec++/g' -e 's/@PROJECT@/OpenRTE/g' -e 's/@PROJECT_SHORT@/ORTE/g' -e 's/@LANGUAGE@/C++/g' < $(top_srcdir)/opal/tools/wrappers/opal_wrapper.1 > ortec++.1
Копировать постоянную ссылку