User forums > Using Code::Blocks

Relative path in output build?

(1/2) > >>

gerardpuducul:
Hy all,

My compiler is a GNU AMR GCC. In is build output, he send me back relative path from the working directory for error and warning. I have modified my parser rule to retrieve the file, line, message information. But when I click on the highlited error in the build log (or build message) nothing happen.

Is codeblock support relative path output debug? Is there a way to support it?


Thanks

for example here is on of my error :

--- Quote ---"..\..\source\th_rf.c", line 487: Serious error: C2291E: <expression> expected but found '/'
--- End quote ---


with my parser rule  :
--- Code: --- (")(.*)("),( line) ([0-9]+):( Error:[ \t].*)
--- End code ---

I have
filename : ..\..\source\th_rf.c
line number : 487
Message : Serious error

MortenMacFly:

--- Quote from: gerardpuducul on December 10, 2008, 06:50:19 pm ---with my parser rule  :
--- Code: --- (")(.*)("),( line) ([0-9]+):( Error:[ \t].*)
--- End code ---

--- End quote ---
What about :
--- Code: --- (")(.*)("),( line) ([0-9]+):( [Ee]rror:[ \t].*)
--- End code ---

gerardpuducul:
Yes of course there is a litlle mistake with my parser rule but this not solve my problem. The parse seems to be done correctly but when i click on the highlited build message nothing happen. Codeblock don't focus on the corrresponding file at the corresponding line (in fact it does nothing). This is why i ask if codeblock support relative path.


Anyway thank for your answer!

Do you have an explaination about this behaviour? can codeblock work with relative path?

thanks

Jenna:
Jumping to relative filenames work for me.

Try this expression:

--- Code: ---"(.*)", line ([0-9]+): (.*)
--- End code ---

and set Message to 3, Filename to 1 and line to 2.

That works for me with your error line:
--- Code: ---Regular expression analyzed as follows:

Type: Error message
Filename: ../../source/th_rf.c
Line number: 487
Message: Serious error: C2291E: <expression> expected but found '/'
--- End code ---

gerardpuducul:
Thanks your parse rule work better that mine (the message error is now complete). But this not solve my problem anymore. :( :(

Maybe due to my special configuration. I use a custom makefile and i launch the make process from a special directory :


--- Code: ---make -C C:\test\toto
--- End code ---

Is it the possible?

thanks

Navigation

[0] Message Index

[#] Next page