Changeset 3581

Timestamp:

Jan 19, 2017, 2:46:51 AM (6 years ago)

Author:

Peter

Message:

refs #878

Make configure try to turn on compiler switches (such as -std=c++11),
so it supports rvalues. If found, #define YAT_HAVE_RVALUE, which can
be used both in source files and in header files. For header files,
<yat/utility/config_public.h> must be #included.

As detailed in README users can turn off cxx11 support when at
configure time of yat, or at compile time of user's package with
preprocessor definition YAT_WITHOUT_CXX.

Location:

trunk

Files:

• README (modified) (1 diff)
• configure.ac (modified) (2 diffs)
• doc/build_tool.doxygen (modified) (1 diff)
• m4/Makefile.am (modified) (1 diff)
• m4/yat_cxx_rvalue.m4 (added)
• yat/utility/config_public.h.in (modified) (1 diff)

trunk/README

@@ -152 +152 @@
   #> ./configure LDFLAGS="-L/usr/lib64/atlas"
 
+=== Rvalues ===
+
+The configure script tries to find a modern compiler that understands
+rvalues and move semantics, and turns on switches such as '-std=c++11'
+if needed. This search can be turned off by invoking
+
+  #> ./configure --without-cxx11
+
+If a compiler with rvalue support is found, macro YAT_HAVE_RVALUE is
+#defined in 'config.h' and move constructors and move assignments is
+available for certain classes plus that moves are used internally. If
+yat is built with rvalue support, yat's header are not compatible with
+a compiler that lack the support. Packages that use autoconf you can
+use macro YAT_CXX_RVALUE, defined in 'm4/yat_cxx_rvalue', to turn on
+the compiler switch in the same fashion as yat's
+configure. Alternatively, yat's choice of compiler with needed
+switches can be accessed via `yat-config --cxx`. If necessary, you can
+turn off rvalue support completely by compiling your program with the
+preprocessor definition YAT_WITHOUT_CXX11.
+
 === Doxygen ===
 

trunk/configure.ac

@@ -86 +86 @@
 m4_ifdef([AM_PROG_AR], [AM_PROG_AR])
 AC_PROG_CXX
+
+AC_ARG_WITH([cxx11],
+            [AS_HELP_STRING([--without-cxx11],
+                            [build with no disable C++11 support])],
+            [],
+            [with_cxx11=yes])
+
+# if CXX11 is wanted look for rvalue support
+yat_have_rvalue=no
+AS_VAR_IF([with_cxx11], [no], [], [
+  YAT_CXX_RVALUE([yat_have_rvalue=yes
+                  AC_DEFINE([YAT_HAVE_RVALUE], [1],
+                            [Define if compiler support rvalues])])
+])
+
 AC_PROG_SED
 AC_PROG_LIBTOOL
@@ -639 +654 @@
   Build Documentation:  $doxygen_message
   With Bam Support:     $with_htslib
+  With Rvalue Support:  $yat_have_rvalue
 
 Options used to compile and link:

trunk/doc/build_tool.doxygen

@@ -41 +41 @@
 OBJECTS=$(SRC:.cc=.o)
 
+CXX=`yat-config --cxx`
 CPPFLAGS+=`yat-config --cppflags`
 CXXFLAGS+=`yat-config --cxxflags`

trunk/m4/Makefile.am

@@ -25 +25 @@
 aclocal_DATA += m4/yat_add_flag.m4
 aclocal_DATA += m4/yat_am_macros.m4
+aclocal_DATA += m4/yat_cxx_rvalue.m4
 aclocal_DATA += m4/yat_cblas.m4
 aclocal_DATA += m4/yat_check_libbam.m4

trunk/yat/utility/config_public.h.in

@@ -56 +56 @@
 #undef YAT_HAVE_BOOST_CONCEPT_WITH_CONSTRUCTOR
 
+/// Don't turn on cxx11 features if user explicitely turned off cxx11.
+#ifndef YAT_WITHOUT_CXX11
+/// Define if compiler support rvalues */
+#undef YAT_HAVE_RVALUE
+#endif
+
 /// Define to 1 if boost::exception_ptr works
 #undef YAT_HAVE_WORKING_BOOST_EXCEPTION_PTR