- C++14 mode not automatic. Was based on compiler version,
but the version of the C++ lib also matters....
Now, there is an explicit USE_CPP14 option [default =OFF]
to set to compile in c++1y mode.
Solve also #89, i.e. the flags is now in TRIQS_CXX_DEFINITIONS and
therefore pass to applications (including ipython magic).
- Python_use_mpi4py is now ON by default.
Rational : it has been used for a while by e.g. Thomas,
and it is necessary on OS X (boost.mpi.python raises a lot of issues).
Hence we put it as default.
- Rename the option Build_Triqs_General_Tools_Test to a simpler
Build_Tests
- new parameter class :
parameters are viewed as form, built in C++, and filled in C++/python.
Each field of the form as a precise C++ type (erased using standard techniques).
First tests ok, to be reread/checked.
TODO : serialization is commented. Lead to long compilation time & large code
due to boost::serialization. Use h5 when possible.
- wrapper :
- separated the converters of the wrapped type in the TRIQS library
- necessary for parameters (it used outside an .so) and potentially
other codes, outside an .so module
- to choose mpi4py over boost.python.mpi, pass -DPython_use_mpi4py=ON
- boost.mpi stays the default for python, but
adding the possibility of using mpi4py instead.
- Due to numerous pbs on recent OS X + brew installation.
boost.mpi does not work (crash in openmpi ??), mpi4py does
- the pytriqs/utility/mpi.py is now configured by the cmake (like
version.py) to prepare one of the two possibilities.
- TODO: not tested carefully : to be done in other machines.
