MantisBT - CMake
View Issue Details
0016012CMakeCMakepublic2016-03-10 20:352016-06-10 14:31
karnmake 
Kitware Robot 
lowtrivialalways
closedmoved 
x86_64linux mint17
CMake 3.5 
 
0016012: CodeBlocks fortran project file contains <Option compiler="gcc"> instead of "gfortran"
Generated project by cmake -G"CodeBlocks - Unix Makefiles" creates project file with <Option compiler="gcc"> but should be <Option compiler="gfortran"> for fortran source files, otherwise codeblocks (version 16.01) cannot properly parse build log, apparently parser is selected by this option, because when I manually replace gcc -> gfortran, cobeblocks successfully parse build log and properly shows (file, line number) of any errors in fortran code.
1. create simple fortran code main.f90:
 program hello
    print *, 'Hello World!'
 end program
2. create CMakeFile:
 project(FortranProject)
 cmake_minimum_required(VERSION 2.8)
 enable_language (Fortran)
 add_executable (fact main.f90)
3. mkdir build; cd build
4. generate codeblocks project file:
 cmake -G"CodeBlocks - Unix Makefiles" -D CMAKE_BUILD_TYPE=Release ..
5. look in FortranProject.cbp, all <Option compiler="gcc">
6. run codeblocksFotran v 1.3, File->Open - select FortranProject.cbp
7. build project - works fine
8. make simple error in fortran source: replace print -> printx
9. build project
10. you can see that there is problem in Build messages window, but file name and line number is missing, so IDE doesn't show where the problem is
11. manually replace in Option compiler="gcc"->"gfortran" in project file FortranProject.cbp, restart IDE and repeat steps 8,9 now after build IDE shows where the problem is.
No tags attached.
Issue History
2016-03-10 20:35karnmakeNew Issue
2016-06-10 14:29Kitware RobotNote Added: 0042963
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0042963)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.