On Tue, 6 Jan 2015 17:58:32 +0000 Timo Betcke <[email protected]> wrote:
> Thanks for your replies. In the past it used to be that Trilinos was > less well tested with Fenics than Petsc. Has this changed now? As we No, Epetra backend was removed from DOLFIN. From Trilinos, just some graph/mesh ordering/partitioning algorithms are optionally used. There's an implementation of TPetra backend on plan and I think that Garth and Chris started working on this. Checkout chris/tpetra branch. Jan > use Trilinos I would not like to also include a Petsc build into our > compilation process. > > Best wishes > > Timo > > On Tuesday, 6 January 2015, Jan Blechta <[email protected]> > wrote: > > > On Mon, 5 Jan 2015 23:45:32 +0000 > > Timo Betcke <[email protected] <javascript:;>> wrote: > > > > > Dear Fenics Team, > > > > > > I am working on the BEM++ (www.bempp.org) Project. We are > > > currently preparing a new release and want to make it easy to > > > interface Fenics for coupled FEM/BEM solves. Claas Abert has > > > already sent me some example code of how to convert Fenics > > > boundary data into a BEM++ Object. > > > > > > As part of the BEM++ installation I would like to offer the > > > ability to also build a core Fenics installation if feasible. Our > > > installer works by automatically downloading add-on libraries and > > > building them as part of the BEM++ installation. > > > > > > My question is what is the minimum set of dependencies necessary > > > to compile a usable Fenics installation? As part of the BEM++ > > > installation we are already downloading/compiling Trilinos, Intel > > > Threading Building Blocks and Armadillo. The default choice for > > > BLAS are MKL as we often get multithreading issues with other Blas > > > libraries (we call into Blas concurrently from multiple threads > > > and unfortunately not every optimised BLAS library is thread > > > safe). > > > > > > What other dependencies would we have to download to be able to > > > compile dolphin and the other Fenics components into a usable > > > package assuming that we stick to a non-MPI build for now. > > > > FIAT requires SymPy. DOLFIN requires > > > > CMake >= 2.8 > > C++11 (C++0x) capable compiler > > Boost >= 1.48 > > Eigen3 > > LibXML2 > > > > Optional packages are > > > > OpenMP > > MPI > > PETSc > > PETSc4py > > SLEPc > > SLEPc4py > > Trilinos > > UMFPACK > > CHOLMOD > > PaStiX > > SCOTCH > > ParMETIS > > zlib > > Python + SWIG >= 2.0 + NumPy > > Sphinx > > HDF5 > > VTK > > QT > > > > Minimally you would probably need LU solver, which is provided by > > PETSc or UMFPACK. > > > > Jan > > > > > > > > Best wishes > > > > > > Timo > > > > > > > > _______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
