Hi Beth,
I see the compiler error message highlighted in the compiler
output presented in console view. It also appears as an item in the
problems view. Neither item will open the source at the offending
line when I click on it.
I tried a synchronized hello world sample program. This sample
program does exhibit what I think is the desired behavior. When I
introduce a bug, the compiler error message is highlighted in the
console view (and there is a corresponding item in the problems
view). Clicking on the highlighted error message opens the
offending file in the editor at the offending line.
This is the behavior I'm trying to reproduce in my "real" project,
but I think the file name paths are getting in the way. There are
no paths in the compiler error message in the hello world sample.
For example,
hello.cpp:12: error: 'oid' was not declared in this scope
hello.cpp:12: error: expected ',' or ';' before '{' token
But there is a full path in the compiler error messages in my "real"
project, perhaps on account of our cmake-generated makefile.
The tool chain is linux-gcc. Are there some settings I need to
adjust on the error parser? Thanks for your thoughts on this, and
have a great day.
-Eric
On 12/07/2012 07:04 AM, Beth Tibbitts wrote:
Eric,
You do mean the error showing
up in the Problems view, not the Console view, right?
The links to source, if
available, should be there, from the error parser for your
compiler, assuming the error parser is set correctly (what
toolchain/compiler are you using?)
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road,
Lexington, KY 40511
"Eric M. Nelson"
---12/06/2012 05:46:55 PM---Dear colleagues, when building
a synchronized project remotely, our compiler is giving
Dear colleagues,
when building a synchronized project remotely, our compiler
is giving
in its error messages the full path name to the source file.
This full
path name on the remote file system does not match the path to
the
source in our local file system, and so eclipse cannot link
from the
error in the console view to opening the appropriate source
file and
jumping to the appropriate line in the c/c++ editor. At least
I presume
this is why the link is not working. Can I get a hint on how
to make
this work? Or a hint on how eclipse makes this identification
between
files on distinct file systems?
Thanks, and have a great day.
-Eric
--
Eric M. Nelson, MS T087, Los Alamos National Laboratory
Los Alamos, NM 87545 Phone: (505)665-6350
E-mail: enelson@xxxxxxxx Fax: (505)667-4420
_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
--
Eric M. Nelson, MS T087, Los Alamos National Laboratory
Los Alamos, NM 87545 Phone: (505)665-6350
E-mail: enelson@xxxxxxxx Fax: (505)667-4420
|