Thank you. This helps. Doesn't Trilinos auto-detect MPI, Python and SWIG file paths ?
Krishna -----Original Message----- From: fipy-boun...@nist.gov [mailto:fipy-boun...@nist.gov] On Behalf Of Guyer, Jonathan E. Dr. (Fed) Sent: Thursday, September 1, 2016 2:27 PM To: FIPY <FIPY@nist.gov> Subject: Re: Essential trilinos packages for Fipy I've been trying to get a conda build of trilinos (and other FiPy prerequisites) put together, but have not had time to ensure that the stack is robust on all platforms. If you're comfortable with conda, what I have is available from the 'guyer' channel at anaconda.org. My current trilinos build recipe is: cmake \ -D CMAKE_BUILD_TYPE:STRING=RELEASE \ -D CMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \ -D DART_TESTING_TIMEOUT:STRING=600 \ -D Trilinos_ENABLE_Fortran:BOOL=OFF \ -D Trilinos_ENABLE_TESTS:BOOL=ON \ -D Trilinos_ENABLE_ALL_OPTIONAL_PACKAGES:BOOL=ON \ -D Trilinos_ENABLE_PyTrilinos:BOOL=ON \ -D Trilinos_ENABLE_Epetra:BOOL=ON \ -D Trilinos_ENABLE_EpetraExt:BOOL=ON \ -D Trilinos_ENABLE_AztecOO:BOOL=ON \ -D Trilinos_ENABLE_ML:BOOL=ON \ -D TPL_ENABLE_MPI:BOOL=ON \ -D MPI_BASE_DIR:PATH=${PREFIX} \ -D BUILD_SHARED_LIBS:BOOL=ON \ -D SWIG_EXECUTABLE:FILEPATH=$PREFIX/bin/swig \ -D CMAKE_INSTALL_PREFIX=$PREFIX \ -D PYTHON_EXECUTABLE:FILEPATH=$PREFIX/bin/python${PY_VER} \ -D PYTHON_INCLUDE_PATH:PATH=$PREFIX/include/python${PY_VER} \ -D PYTHON_LIBRARY:FILEPATH=$PREFIX/lib/libpython${PY_VER}.${SO_EXT} \ -D PyTrilinos_INSTALL_PREFIX:PATH=$PREFIX \ -D BLAS_LIBRARY_DIRS=${PREFIX}/lib \ -D BLAS_LIBRARY_NAMES="openblas;libgfortran.so.1" \ -D LAPACK_LIBRARY_DIRS=${PREFIX}/lib \ -D LAPACK_LIBRARY_NAMES="openblas" \ .. I have not critically evaluated everything in this; I've just been trying to get a build that FiPy can work with. > On Aug 31, 2016, at 7:00 PM, Krishna <krishnaku...@imperial.ac.uk> wrote: > > Hi, > > We are at a stage wherein we can aim to scale up our serial FiPy code to > multiple cores. > > The Trilinos suite consists of ki numerous packages, which takes a > considerable amount of time to build. Thus, the official recommendation from > Sandia is to build only those packages which are absolutely necessary. > > I'd like to ask the developers of FiPy if there exists a list of these > essential bare-minimum packages to get FiPy running in parallel. > > Best Regards, > > Krishna > > _______________________________________________ > fipy mailing list > fipy@nist.gov > http://www.ctcms.nist.gov/fipy > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] _______________________________________________ fipy mailing list fipy@nist.gov http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] _______________________________________________ fipy mailing list fipy@nist.gov http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
