gfortran 4.5.2 (f95) compile definitions fix
authorDawid Jagiela <lightnir@chem.univ.gda.pl>
Tue, 8 May 2012 11:53:44 +0000 (13:53 +0200)
committerDawid Jagiela <lightnir@chem.univ.gda.pl>
Tue, 8 May 2012 11:53:44 +0000 (13:53 +0200)
CMakeLists.txt

index c084cff..b4e0cae 100644 (file)
@@ -28,7 +28,7 @@ get_filename_component (Fortran_COMPILER_NAME ${CMAKE_Fortran_COMPILER} NAME)
 
 # Altough cmake enables you to set some compiler definitions it seems by default they are ignored.                 
 # This is a workaround to pass compiler definitions (preprocesor flags) to fortran compilers like ifort
-SET(CMAKE_Fortran_COMPILE_OBJECT "<CMAKE_Fortran_COMPILER>  ${CMAKE_START_TEMP_FILE} <FLAGS> <DEFINES> <SOURCE> -o <OBJECT> ${CMAKE_END_TEMP_FILE}")
+SET(CMAKE_Fortran_COMPILE_OBJECT "<CMAKE_Fortran_COMPILER>  ${CMAKE_START_TEMP_FILE} <FLAGS> <DEFINES> -c <SOURCE> -o <OBJECT> ${CMAKE_END_TEMP_FILE}")
 #set(CPPFLAGS "-DPROCOR -DLINUX -DPGI -DUNRES -DISNAN -DMP -DMPI -DSPLITELE -DLANGO -DCRYST_BOND -DCRYST_THETA -DCRYST_SC" )
 #add_definitions( ${CPPFLAGS} )