CMake.git - CMake is a cross-platform, open-source build system generator.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Various typo fixes	Luz Paz	2018-01-03	1	-2/+2
\| \| \| \|	Some are user-facing. Others are source comments.
*	CheckFortranCompilerFlag: Add test case	Brad King	2015-02-05	1	-0/+7
\| \| \| \|	Extend the FortranOnly test with a case covering this module.
*	Makefile: Add assembly and preprocessed targets for Fortran	Tim Gallagher	2014-11-10	3	-0/+38
\| \| \| \|	Extend the FortranOnly test to cover "make <src>.i" targets.
*	VS: Support Intel Fortran 15 .vfproj generation (#15175)	Brad King	2014-09-30	1	-8/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This version of the Intel Fortran plugin to Visual Studio says: please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile) We must set TargetName and TargetExt in addition to the existing setting for OutputDirectory. The settings do not appear to hurt older versions of Intel Fortran, so set them unconditionally. Extend the FortranOnly test to cover a corresponding use case by using the OUTPUT_NAME target property. Inspired-by: Ian Harvey <Ian.Harvey@megms.com.au>
*	Add CheckFortranSourceCompiles module (#14656)	Brad King	2014-08-18	1	-0/+22
\| \| \| \| \| \| \|	Copy the CheckCSourceCompiles module and port it to Fortran. Extend the FortranOnly test to try using the new module. Suggested-by: Nicolas Bock <nicolasbock@gmail.com>
*	Fortran: Add support for free- and fixed-form flags	Brad King	2011-08-31	2	-5/+7
\| \| \| \| \| \| \|	Define a "Fortran_FORMAT" target and source file property. Initialize the target property from a "CMAKE_Fortran_FORMAT" variable. Interpret values "FIXED" and "FREE" to indicate the source file format. Append corresponding flags to the compiler command line.
*	Fix custom commands in VS2010 Fortran projects using CFG_INTDIR and test.	Bill Hoffman	2011-08-03	6	-0/+73
	For custom commands in VS2010 Fortran projects the INTDIR variable is different than in the rest of the solution because Intel fortran still uses the old VS project files even in VS2010. So, we replace $(Configuration) directly in the project files. I have also added a FortranOnly test that tests this feature and is run on any generator that has Fortran abilities.