User forums > Using Code::Blocks

When compilation fails, how can I jump to the line that has the error?

<< < (2/2)

erezz:

--- Quote from: ToApolytoXaos on October 23, 2013, 03:36:04 pm ---
--- Quote from: erezz on October 23, 2013, 11:27:20 am ---Hi,

I'm using version 12.11 on Ubuntu 12.04. I'm compiling my code on a remote machine with a ssh command. This works well.

When compilation fails, I see the error messages in the "Build log" tab and the "Build messages" tab. I would like to be able to double-click (or something similar) the error message and jump directly to the line that caused the compilation error. Is this possible? How? I couldn't google a solution for that.

Thanks,
Erez

--- End quote ---
You mean you are using a secure way to communicate to a remote PC that uses graphical user inteface and you want to access the error line by simply press the error message, am I correct? If yes, this is the default way error log tab works, as I am pressing it myself to take me to the actual <filename>-line:column. To clarify something though, I don't know if this option was added before the release of 12.11, but I always use the latest revision and the latest GCC (currently 4.8.1) as I am compiling it myself if this helps a bit.

--- End quote ---

I running a ssh command that executes the make command on a remote machine, no GUI at all on the remote machine.

Was it added after 12.11?

Thanks,
Erez

oBFusCATed:

--- Quote from: erezz on October 23, 2013, 07:54:52 pm ---I running a ssh command that executes the make command on a remote machine, no GUI at all on the remote machine.

--- End quote ---
So, it seems that you're using makefile based build and not the native build system of codeblocks, aren't you?
Can you post part of the build log which contains some error messages?

erezz:
Yes, I'm using a makefile based build and not the native build system of codeblocks. I've attached a screenshot of the error messages.

oBFusCATed:
Where is your Makefile located?
If it is not next to the cbp file, opening files won't work.

Navigation

[0] Message Index

[*] Previous page

Go to full version