Output parser, click misbehaviour

Discussion Forums discussion Output parser, click misbehaviour

This topic contains 0 voices and has 3 replies.

Viewing 4 posts - 1 through 4 (of 4 total)
Author Posts
Author Posts
December 11, 2007 at 1:28 pm #316

ellsv
Member

Hi!

Thanks for an quite excellent IDE for embedded C/C++ programming.

Have a problem though, with the output parser, or more, a misbehaviour from PN when clicking on a compiler error.

If the file I am compiling is already open for editing in PN, and I click on a compiler error in the output window, PN opens a new instance of the already opened file.

Is this a known issue or? I’ve scrolled through the topics in this discussion-group and also looked in the BUG database, and have not seen anything on this.

Is it worth a fix?

Thanks

/ellsv

January 2, 2008 at 2:14 pm #15682

simon
Key Master

It shouldn’t do that, so it will be something to do with how the path in the output window not being easy to compare to the path PN thinks the file is in. Can you please show me some output from the compiler where this happens, and give me the full path of the file on the disk that it’s trying to open.

Thanks.

January 14, 2008 at 11:01 am #15683

ellsv
Member

Hi!

Thanks!

You’re right. This is what’s shown in the ouput:

proj/test/main.cpp:66: error: `displ’ does not name a type

And this is the location of the file:

c:projtestmain.cpp

I added a “C:” in my makefile, so for me this is not a (big) issue any more.

The main reason that the path, in the output, looks like this is because I use a cygwin based compiler toolchain.

Thanks again

/ellsv

January 21, 2008 at 12:54 pm #15684

simon
Key Master

ok thanks for the update, I’ll look into improving this in the future.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.