[cmake-developers] Fortran detection, issue 9220

[Alan W. Irwin]

On 2015-02-10 22:38-0500 Ben Boeckel wrote:

> On Tue, Feb 10, 2015 at 17:15:33 -0800, Alan W. Irwin wrote:
>> As the originator (almost 6 years ago) of this bug report I am still
>> very much interested in a fundamental solution to give a WARNING
>> message rather than an error if there is any issue with a compiler.
>
> This patch makes it only an error when Ninja detects a Fortran compiler
> rule being written (which is where the actual incompatibility lies).

Sorry, but I still think the general Ninja problems with Fortran are
orthogonal to this general language support issue.  Or are you
implying that enable_language(OPTIONAL) works for Ninja now for all
languages other than Fortran?

> Other languages error out because CMake doesn't have *any* knowledge of
> how to build them. Java is kinda-sorta there IIRC. I haven't used it
> much, but I don't remember it feeling first-class.

I frankly don't understand this comment at all. I am sure you would
agree with me that CMake has complete knowledge of how to build
applications and libraries with a wide variety of compilers.  So I
probably just completely missed your point.

> [...P]utting logic behind enable_language(OPTIONAL) would be nice.

Agreed.  It's probably an extremely tedious task to go through all the
code paths (including all generators and all compiled languages) for
modern CMake language support that are executed by the
enable_language(... OPTIONAL) command, and change all potential CMake
error exits to warnings for that case.  And I don't have the C++ skill
or knowledge of CMake internals to help out with this tedious task
myself.  So I completely understand why a fix for bug 9220 has still not been
accomplished after all these years.  But it sure is a "would be nice".

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________