Permit disabling Fortran Interfaces

[nicholasmalaya]

Let's leave them on by default (it is the language of scientific computing!) but permit disabling construction by passing a flag, such as --disable-fortan-interfaces

This may help encourage more general MASA use.

[RhysU]

Should be possible to autodetect without needing a flag. Look at the
Autoconf. Could take a stab early next week if you like.

• Rhys
  On Feb 27, 2015 6:44 PM, "Nicholas Malaya" notifications@github.com wrote:

Let's leave them on by default (it is the language of scientific
computing!) but permit disabling construction by passing a flag, such as
--disable-fortan-interfaces

This may help encourage more general MASA use.

—
Reply to this email directly or view it on GitHub
#24.

[koomie]

While that would be trivial, I would be in favor of asking the user to opt out if they don’t want it. That’s better in my mind to avoid building/installing in an environment that may need some extra flags set to define FC (e.g. building support for vendor compilers) and having things seemingly go ok, only to have a user find out later that their fortran symbols are missing.

Perhaps a compromise would be to put some extra language around the Fortran test to notify the user that there is a “—disable-fortran” option if the autoconf fortran test fails?

On Feb 27, 2015, at Feb 27, 5:49 PM, Rhys Ulerich notifications@github.com wrote:

Should be possible to autodetect without needing a flag. Look at the
Autoconf. Could take a stab early next week if you like.

• Rhys
  On Feb 27, 2015 6:44 PM, "Nicholas Malaya" notifications@github.com wrote:

Let's leave them on by default (it is the language of scientific
computing!) but permit disabling construction by passing a flag, such as
--disable-fortan-interfaces

This may help encourage more general MASA use.

—
Reply to this email directly or view it on GitHub
#24.

—
Reply to this email directly or view it on GitHub #24 (comment).

[nicholasmalaya]

Merged in #25