dft_tools/pytriqs/utility/CMakeLists.txt


SET(PYTHON_SOURCES 
  ${CMAKE_CURRENT_SOURCE_DIR}/__init__.py
  ${CMAKE_CURRENT_SOURCE_DIR}/dichotomy.py
  ${CMAKE_CURRENT_SOURCE_DIR}/dist_on_nodes.py
  ${CMAKE_CURRENT_BINARY_DIR}/mpi.py
  ${CMAKE_CURRENT_BINARY_DIR}/mpi_mpi4py.py
  ${CMAKE_CURRENT_BINARY_DIR}/mpi_boost.py
  ${CMAKE_CURRENT_SOURCE_DIR}/redirect.py
)

install (FILES ${PYTHON_SOURCES} DESTINATION ${TRIQS_PYTHON_LIB_DEST}/utility)
First commit : triqs libs version 1.0 alpha1 for earlier commits, see TRIQS0.x repository. 2013-07-17 19:24:07 +02:00
			`SET(PYTHON_SOURCES`
			`${CMAKE_CURRENT_SOURCE_DIR}/__init__.py`
			`${CMAKE_CURRENT_SOURCE_DIR}/dichotomy.py`
			`${CMAKE_CURRENT_SOURCE_DIR}/dist_on_nodes.py`
pytriqs: add option to use mpi4py instead of boost.python.mpi - 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. 2013-12-29 13:43:38 +01:00			`${CMAKE_CURRENT_BINARY_DIR}/mpi.py`
			`${CMAKE_CURRENT_BINARY_DIR}/mpi_mpi4py.py`
			`${CMAKE_CURRENT_BINARY_DIR}/mpi_boost.py`
First commit : triqs libs version 1.0 alpha1 for earlier commits, see TRIQS0.x repository. 2013-07-17 19:24:07 +02:00			`${CMAKE_CURRENT_SOURCE_DIR}/redirect.py`
			`)`

			`install (FILES ${PYTHON_SOURCES} DESTINATION ${TRIQS_PYTHON_LIB_DEST}/utility)`