[MOAB-dev] Disable fortran in moab-5.0.0

[Vijay S. Mahadevan]

Paul, as Lorenzo mentioned, we need to modify configuration to enable
this cross option. I can look into that as well.

The more combinations/options we add, the more complicated the
configuration becomes. While things do become seemingly flexible, I
just want to make sure it doesn't become a maintenance nightmare later
on. Hence the decision originally to just make BLAS/LAPACK mandatory
and not allow Eigen (with/without external BLAS). The implication on
FC here was a side effect unfortunately of that decision.

Vijay

On Fri, Nov 10, 2017 at 3:29 PM, Lorenzo Botti <bottilorenzo at gmail.com> wrote:
> Dear Paul,
> I don’t think it’s actually possible. The build system should be modified to
> account for such a configure option.
> Anyway this is also what I need, a fix to run MOAB on OSX without fortran.
> On my laptop I’m not interested on performance but I do most of the
> development.
> Installing a fortran compiler on OSX is a pain, as far as I know this forces
> me to use gcc instead of clang.
> Accordingly I would need to use a package manager like macports or homebrew,
> or to compile gcc myself.
> A fallback on Eigen would be really welcome.
>
> Bests
> Lorenzo
>
> On 10 Nov 2017, at 21:19, Paul Wilson <paul.wilson at wisc.edu> wrote:
>
> I'm not sure if I follow how to actually do what you are suggesting.  If I
> wanted to rely on Eigen instead of both BLAS/LAPACK, is there a set of
> options I can pass to either autoconf or CMAKE to do that?
>
>