On 2008-09-22 18:25-0400 Bill Hoffman wrote:
Another approach might be to use enable_language(languageName OPTIONAL).
Would this work:
enable_language(Fortran OPTIONAL)
project(myproject C CXX)
It would always test for fortran, and enable it if they have it. If they do
not have it, then you can just turn off that binding. It won't be an error
not to have it. If they do have it you can offer the binding option for
Fortran.
In fact, I have been considering moving to that approach since it should
give a smoother user experience.
However, that consideration doesn't affect the principal issue which is that
our current approach and the above approach still must use ENABLE_LANGUAGE
for optional languages like Fortran. This means the ENABLE_LANGUAGE bug
kicks in for Fortran, the Fortran compiler flags are not set properly in the
cache for PLplot, and build types do not work properly for the Fortran
binding of PLplot (on the Linux platform).
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); PLplot scientific plotting software
package (plplot.org); 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
__________________________
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
