User forums > Using Code::Blocks

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

(1/3) > >>

pclausen:
Hi

I'm working as developer on Linux using mainly C/C++ and Fortran (Intel Compilers: icpc and ifort). We have been looking for a new IDE since the C-Forge project died. Due to CMake and the integration of C::B therein I wanted to take a look into the Pros/Cons of C::B. The competition is Eclipse and Kdevelop.

My general first impression is really good. The Fortran Plugin http://darmar.vgtu.lt looks really neat but I have to see how it really performs in our mixed C++ and Fortran 90-code.

I have exported our CMake-project and its really beautifully imported into C::B. It would have been nice if compiler settings were also read from CMake but that does not matter much - I can live with changing that manually.

I have two main issues:
1. Perforce integration: We use Perforce which means that Perforce integration is pretty much a KO-criterion. However, it would be sufficient to simply being able to check out files when editing. Something like:
   $ p4 edit $current_file_in_CB$
Can I add this myself or hack it somehow? A button in C::B doing the above would also be OK.

2. Fortran compiler jump to error does not work. The output of ifort i a bit different than icpc but I read somewhere that C::B uses regex's to parse the output. Can I somehow fix it myself or have I overlooked some setting ?

--- Code: ---IFORT: fortcom: Error: /scratch/users/clausen/Repository/main/development/baseline/source/prog_dev/prog_hp2/bead_steu.f90, line 69: A specification statement cannot appear in the executable section.
ICPC: /scratch/users/clausen/Repository/main/development/baseline/source/onf/fem2onf/fem2onf.cpp(30): error: identifier "dflmdfb" is undefined

--- End code ---

I am uncertain whether I'm posting in the correct tread because I am not that experienced in posting in forums. Thanks in advance for you advice.

Best regards

Peter

oBFusCATed:
You can modify the parsing in:
Settings -> Compiler & Debugger -> Compiler -> Ifort -> Other settings -> Advanced button -> Output parsing...

If you fix the parsing probably you could provide a patch :)

killerbot:
I have once written a plug-in for clearcase, I think it can be used as a starting point and changing it a bit so it works for perforce might not be that difficult.
I might be able to help on this, if you could provide me the commands to execute (so I don't have to read too much of the manual ;-) ).
I experimented with perforce about 8 years ago, but I ahve been planning of reinstating it at home as my personal version control system.

So let's say the perforce issue could be solved, maybe insmall increments, but at least there will be progress.

pclausen:
@oBFusCATed: Thanks, I'll look into that

@killerbot: That sounds cool. I'll try to list what I use  - which may only be a subset of what most people use, but hey that a starting point. There is a free Perforce-download at: http://www.perforce.com/perforce/download_eval.html

Important Perforce (p4) commands
The only thing I am really really missing is "check out current file" which is


--- Code: ---$ p4 edit <current_file>
--- End code ---

if this can be automatically done by "Replace in files ..." I would be laughing !  :-D

Often used Perforce (p4) commands
Our usual workflow is to only checkout in the IDE. I have even done a bit of Python programming in Eclipse which has a full blown Perforce integration, but I (and my colleagues) mostly use Perforce's own client (P4v) for the rest (submit, adding files, ...).

For IDE integratino you would need to know if a file is in source control or not. This can be done in different ways but I guess following should do the job:

--- Code: ---p4 files *
//depot/main/development/baseline/source/CMakeLists.txt#17 - edit change 46261 (text)
CMakeLists.txt~ - no such file(s).

--- End code ---

Often used commands would be:

        sync       Synchronize the client with its view of the depot

--- Code: ---p4 sync ./...
--- End code ---
                     Above Syncs current dir and subdirs
        add        Open a new file to add it to the depot
        edit       Open an existing file for edit
        delete     Open an existing file to delete it from the depot

        resolve    Merge open files with other revisions or files
        revert     Discard changes from an opened file
        submit     Submit open files to the depot

And also:

        change      Create or edit a changelist description
        diff        Display diff of client file with depot file
        diff2       Display diff of two depot files
        filelog     List revision history of files

Of course Perforce is capable of much more (about 85 commands) and we are only using the outmost basics.

If I can in any way help to test I would be very happy. Compiling is no problem (I guess) but I have never done GUI-programming...

Best regards

Peter

oBFusCATed:

--- Quote from: pclausen on November 10, 2010, 05:31:20 pm ---The only thing I am really really missing is "check out current file" which is


--- Code: ---$ p4 edit <current_file>
--- End code ---

--- End quote ---
You can add a tool for that -> Tools -> Configure tools

Navigation

[0] Message Index

[#] Next page