User forums > Using Code::Blocks

First impression of C::B - Perforce and Intel Fortran issues

<< < (2/3) > >>

pclausen:
WOW, that's pretty cool !

I've added: Tools --> Configure Tools --> Add ...
Name: P4Edit
Executable: /store2/develop/perforce/p4
Parameters: edit ${ACTIVE_EDITOR_FILENAME}

* Launch tool hidden with standard output redirect

Thus, I can edit files by just: ctrl-E  using a shortcut: Settings --> Editor --> Keyboard Shortcuts

I've added the ifort regex (must be moved before the C-regexes, dont really know why)
Settings -> Compiler & Debugger -> Compiler -> Ifort -> Other settings -> Advanced button -> Output parsing...

Description: Compilation error ifort
Type: Error
Regex: fortcom:[ \t]+[Ee]rror[ \t]*:[ \t]*([{}() \t#%$~A-Za-z0-9_:+/\.-]+)[, \t]+line[ \t]+([0-9]+)[: \t]+(.*)
Message: 3
Filename: 1
Line:2


Description: Compilation warning ifort
Type: Error
Regex: fortcom:[ \t]+[Ww]arning[ \t]*:[ \t]*([{}() \t#%$~A-Za-z0-9_:+/\.-]+)[, \t]+line[ \t]+([0-9]+)[: \t]+(.*)
Message: 3
Filename: 1
Line:2

Thumbs up and thanks guys! Could you add this to the Intel-compiler options by default? I do not see why not...

One minor issue: If line nr is 0 (happens when Fortran names are too long) then Code::Blocks cant jump to file. Example compiler output:

--- Code: ---fortcom: Warning: /scratch/users/clausen/Repository/main/development/baseline/source/prog_dev/prog_mod/s_cell_reg.f90, line 0: Global name too long, shortened from: cell_raster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_command_id_name_ to: ll_raster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_command_id_name_
--- End code ---

I'll be back when I have some more experience with C::B

/Peter

xunxun:

--- Quote from: pclausen on November 11, 2010, 11:35:30 am ---One minor issue: If line nr is 0 (happens when Fortran names are too long) then Code::Blocks cant jump to file. Example compiler output:

--- Code: ---fortcom: Warning: /scratch/users/clausen/Repository/main/development/baseline/source/prog_dev/prog_mod/s_cell_reg.f90, line 0: Global name too long, shortened from: cell_raster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_command_id_name_ to: ll_raster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_command_id_name_
--- End code ---

I'll be back when I have some more experience with C::B

/Peter

--- End quote ---

This is a warnning, and you can add a warning regx rule.

pclausen:

--- Quote from: xunxun1982 on November 11, 2010, 04:57:56 pm ---This is a warnning, and you can add a warning regx rule.

--- End quote ---

Yes I know, and all other warnings work - but not when line number = 0 as it is in this case.

/Peter

xunxun:

--- Quote from: pclausen on November 12, 2010, 12:01:31 pm ---
--- Quote from: xunxun1982 on November 11, 2010, 04:57:56 pm ---This is a warnning, and you can add a warning regx rule.

--- End quote ---

Yes I know, and all other warnings work - but not when line number = 0 as it is in this case.

/Peter



--- End quote ---

Could you show your some source code? I don't know what "Fortran names are too long"'s meaning is. I think "Fortran names are too long" may occur some error as "This symbol has too many characters".

pclausen:
Its been a while - and I still like Code::Blocks   :D


--- Quote from: xunxun1982 on November 12, 2010, 04:56:38 pm ---Could you show your some source code? I don't know what "Fortran names are too long"'s meaning is. I think "Fortran names are too long" may occur some error as "This symbol has too many characters".

--- End quote ---

The code is:

--- Code: ---MODULE CELL_RASTER
.....
contains
  subroutine s_get_nd_in_area_gad_brute_force (minp, &
    &                                          maxp)
    use coordinate_transformation
    ...
   end subroutine

--- End code ---

Generates the warning:


--- Code: ---fortcom: Warning: /scratch/users/clausen/Repository/main/development/baseline/source/prog_dev/prog_mod/s_cell_reg.f90, line 0: Global name too long, shortened from: cell_raster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_design_cycle_aktuell_ to: ster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_design_cycle_aktuell_

--- End code ---
I fixed it by including the USE-statement in the top of module statement - the way it should be! Still, Code::Blocks chokes on the "line 0"

Navigation

[0] Message Index

[#] Next page

[*] Previous page