Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Mapping error message path to Eclipse file
Mapping error message path to Eclipse file [message #228916] Mon, 19 January 2009 01:48 Go to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Hi,

I'm using Eclipse to debug QEMU simulator.
When compiling this project, Cygwin produces error messages with path to
file like

/cygdrive/d/Dvs/Project/qemu-0.9.1/hw/omap.c:118: undefined reference to
`ffs'

These message are shown at the Problems view but not operable: I cannot go
to source by clicking at the problem.

Most likely, Eclipse/CDT cannot map /cygdrive/d/ to D:\

Is there any way to tell Eclipse how to do this?

Dmitry.
Re: Mapping error message path to Eclipse file [message #228939 is a reply to message #228916] Mon, 19 January 2009 09:02 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

> I'm using Eclipse to debug QEMU simulator.
> When compiling this project, Cygwin produces error messages with path to
> file like

> /cygdrive/d/Dvs/Project/qemu-0.9.1/hw/omap.c:118: undefined reference to
> `ffs'

> These message are shown at the Problems view but not operable: I cannot go
> to source by clicking at the problem.

> Most likely, Eclipse/CDT cannot map /cygdrive/d/ to D:

> Is there any way to tell Eclipse how to do this?

Couple of questions:
- Is this path inside your project?
- Is there another file omap.c in a different folder in the project?

I can try to help solving your particular problem, but I think the cygwin
issue with that warrants opening a bug in bugzilla. Can you do that?

Andrew
Re: Mapping error message path to Eclipse file [message #229030 is a reply to message #228939] Tue, 20 January 2009 06:44 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Andrew Gvozdev wrote:

> Dmitry Smirnov wrote:
...
>> /cygdrive/d/Dvs/Project/qemu-0.9.1/hw/omap.c:118: undefined reference to
>> `ffs'


> Couple of questions:
> - Is this path inside your project?

Yes. QEMU/qemu-0.9.1/hw/omap.c
I have to note that QEMU is the project name, qemu-0.9.1 is the Linked
folder mapped to D:\Dvs\Project\qemu-0.9.1. I suppose this issue does not
depend on Linked Forder usage.

> - Is there another file omap.c in a different folder in the project?

No, there is no more files with this name.

> I can try to help solving your particular problem, but I think the cygwin
> issue with that warrants opening a bug in bugzilla. Can you do that?

I will.

I would like to mention that Debug Congurations seems to support this kind
of mapping through Source Lookup Path (manually configured). Perhaps this
could be expanded to Error Parsers?

Dmitry
Re: Mapping error message path to Eclipse file [message #229054 is a reply to message #229030] Tue, 20 January 2009 09:47 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:
>>> /cygdrive/d/Dvs/Project/qemu-0.9.1/hw/omap.c:118: undefined reference to
>>> `ffs'
>> Couple of questions:
>> - Is this path inside your project?
> Yes. QEMU/qemu-0.9.1/hw/omap.c
> I have to note that QEMU is the project name, qemu-0.9.1 is the Linked
> folder mapped to D:DvsProjectqemu-0.9.1. I suppose this issue does not
> depend on Linked Forder usage.
>> - Is there another file omap.c in a different folder in the project?
> No, there is no more files with this name.

Seems to work for me with linked folder on cygwin. Can you try most recent
CDT build? There were a couple bugs fixed recently related to that.

>> I can try to help solving your particular problem, but I think the cygwin
>> issue with that warrants opening a bug in bugzilla. Can you do that?
> I will.
Perhaps it is not necessary if the latest build works for you.

> I would like to mention that Debug Congurations seems to support this kind
> of mapping through Source Lookup Path (manually configured). Perhaps this
> could be expanded to Error Parsers?
How do you configure that?

Andrew

> Dmitry
Re: Mapping error message path to Eclipse file [message #229061 is a reply to message #229054] Tue, 20 January 2009 10:55 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Andrew Gvozdev wrote:

> Seems to work for me with linked folder on cygwin. Can you try most recent
> CDT build? There were a couple bugs fixed recently related to that.
I'm using
Eclipse Platform Version: 3.4.1 Build id: M20080911-1700
Eclipse C/C++ Development Tools Version: 5.0.1.200809120802 Build id:
200809120802

Do you mean any newer?

>> I would like to mention that Debug Congurations seems to support this kind
>> of mapping through Source Lookup Path (manually configured). Perhaps this
>> could be expanded to Error Parsers?
> How do you configure that?
If you mean Debug Configuration, I never configured it, it wasn't needed
for my other projects. But I know that I can create Path Mapping and map
/cygdrive/d to D:\, for instance.

Is it possible that some cygwin (or system) configuration lead to this
issue?
How Eclipse maps such cygwin path to local file system? Does it use
cygpath utility?

Dmitry
Re: Mapping error message path to Eclipse file [message #229076 is a reply to message #229061] Tue, 20 January 2009 12:39 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

>> Seems to work for me with linked folder on cygwin. Can you try most recent
>> CDT build? There were a couple bugs fixed recently related to that.
> I'm using
> Eclipse Platform Version: 3.4.1 Build id: M20080911-1700
> Eclipse C/C++ Development Tools Version: 5.0.1.200809120802 Build id:
> 200809120802
> Do you mean any newer?

Yeah I meant Eclipse 3.5 & CDT 6.0 latest build from
http://download.eclipse.org/tools/cdt/builds/

But I tried it with your version which is CDT 5.0.1 Final and it works for
me just fine. Not sure what could be the problem.

Andrew

> Dmitry
Re: Mapping error message path to Eclipse file [message #229097 is a reply to message #229076] Wed, 21 January 2009 03:27 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
I'm going to debug the issue.

Could you please tell me what is displayed in your Console View and
Problem View? Do you see same Cygwin path (like /cygwin/d/) in both views?

Dmitry
Re: Mapping error message path to Eclipse file [message #229104 is a reply to message #228916] Wed, 21 January 2009 03:47 Go to previous messageGo to next message
Axel Mueller is currently offline Axel Mueller
Messages: 1926
Registered: July 2009
Senior Member
I have a similar problem and no solution :-(.
I am using the MS Visual C++ compiler on Linux with Wine. So I can compile
for Linux (gcc) and Windows(msvc) on the same platform at the same time.
The compiler output (cl.exe) uses, of course, Windows style path but
Eclipse expects Linux paths. A path mapping from Wine to Linux would be
very helpful to be able to click errors/warning in the Problem View.

Axel

> Hi,

> I'm using Eclipse to debug QEMU simulator.
> When compiling this project, Cygwin produces error messages with path to
> file like

> /cygdrive/d/Dvs/Project/qemu-0.9.1/hw/omap.c:118: undefined reference to
> `ffs'

> These message are shown at the Problems view but not operable: I cannot go
> to source by clicking at the problem.

> Most likely, Eclipse/CDT cannot map /cygdrive/d/ to D:

> Is there any way to tell Eclipse how to do this?

> Dmitry.


Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google
Re: Mapping error message path to Eclipse file [message #229111 is a reply to message #229097] Wed, 21 January 2009 04:14 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Dmitry Smirnov wrote:

When path is processed by GCCErrorParser, it finally goes to
ErrorParserManager.findFilePath.

This method fails to find the file in usual way and tries to use cygpath.
This was successfull and cygpath returns
D:\Dvs\Project\qemu-0.9.1\hw\omap.c (at ErrorParserManager.java:334.

Then at line 337 it is converted to hw\omap.c (i.e. relative to project
root) and file was found in workspace at line 341. Its path is
/QEMU/hw/omap.c.

At line 353 the relative path hw\omap.c (not the path of the file found in
workspace) is converted to canonical path. The result of this conversion
is D:\EclipseGanymedeSR1\hw\omap.c !!

D:\EclipseGanymedeSR1 is the path where my Eclipse is installed.

Thus, mapping to a file is failed and error message is attached to a
project...
Re: Mapping error message path to Eclipse file [message #229128 is a reply to message #229111] Wed, 21 January 2009 10:52 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Hi there,
I tried to follow your steps in debugger and got slightly different
results.

Dmitry Smirnov wrote:
> When path is processed by GCCErrorParser, it finally goes to
> ErrorParserManager.findFilePath.
> This method fails to find the file in usual way and tries to use cygpath.
> This was successfull and cygpath returns
> D:DvsProjectqemu-0.9.1hwomap.c (at ErrorParserManager.java:334.
So far so good.

> Then at line 337 it is converted to hwomap.c (i.e. relative to project
> root) and file was found in workspace at line 341. Its path is
> /QEMU/hw/omap.c.
I am not getting to line 337. The condition on line 311
fBaseDirectory.isPrefixOf(fp) is false and I get to line 315 so the proper
marker is generated.
fBaseDirectory=E:/EclipseGanymedeSR1/runtime-EclipseApplicat ion/QEMU and
fp=/cygdrive/e/Dvs/Project/qemu-0.9.1/hw/omap.c (using drive E: for the
test). Nothing in common. What is your fBaseDirectory?

Andrew

> At line 353 the relative path hwomap.c (not the path of the file found in
> workspace) is converted to canonical path. The result of this conversion
> is D:EclipseGanymedeSR1hwomap.c !!

> D:EclipseGanymedeSR1 is the path where my Eclipse is installed.

> Thus, mapping to a file is failed and error message is attached to a
> project...
Re: Mapping error message path to Eclipse file [message #229134 is a reply to message #229128] Wed, 21 January 2009 11:51 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Andrew Gvozdev wrote:

> Hi there,
> I tried to follow your steps in debugger and got slightly different
> results.


>> Then at line 337 it is converted to hwomap.c (i.e. relative to project
>> root) and file was found in workspace at line 341. Its path is
>> /QEMU/hw/omap.c.
> I am not getting to line 337. The condition on line 311
> fBaseDirectory.isPrefixOf(fp) is false and I get to line 315 so the proper
> marker is generated.
> fBaseDirectory=E:/EclipseGanymedeSR1/runtime-EclipseApplicat ion/QEMU and
> fp=/cygdrive/e/Dvs/Project/qemu-0.9.1/hw/omap.c (using drive E: for the
> test). Nothing in common. What is your fBaseDirectory?

D:/Dvs/Project/qemu-0.9.1
This value was applied in initErrorParserManager. Argument
('workingDirectory') have the same value.
Build location of the project was set up as
${workspace_loc:/QEMU/qemu-0.9.1}

Dmitry
Re: Mapping error message path to Eclipse file [message #229142 is a reply to message #229134] Wed, 21 January 2009 12:43 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

> Build location of the project was set up as
> ${workspace_loc:/QEMU/qemu-0.9.1}

After setting Build location this way I am able to reproduce the issue.
This suggests to move your build location elsewhere as workaround.

I'll file a bug on that in bugzilla.

Thanks,
Andrew
Re: Mapping error message path to Eclipse file [message #229150 is a reply to message #229142] Wed, 21 January 2009 16:17 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
> I'll file a bug on that in bugzilla.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261913
Re: Mapping error message path to Eclipse file [message #229166 is a reply to message #229150] Thu, 22 January 2009 02:08 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Well, my project is a makefile project.
I do not know straightforward way to change directory from Eclipse
directly. At least, build command like
cd ${workspace_loc:/QEMU/qemu-0.9.1} && make
does not work.

So, I created gotodir.cmd in the ${workspace_loc:/QEMU} and use the
following command
gotodir.cmd ${workspace_loc:/QEMU/qemu-0.9.1}

Content of the gotodir.cmd is

cd %1
make

Dmitry
Re: Mapping error message path to Eclipse file [message #229173 is a reply to message #229166] Thu, 22 January 2009 02:18 Go to previous messageGo to next message
Axel Mueller is currently offline Axel Mueller
Messages: 1926
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

> Well, my project is a makefile project.
> I do not know straightforward way to change directory from Eclipse
> directly. At least, build command like
> cd ${workspace_loc:/QEMU/qemu-0.9.1} && make
> does not work.
Try this:
make -C ${workspace_loc:/QEMU/qemu-0.9.1}

Axel


Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google
Re: Mapping error message path to Eclipse file [message #229181 is a reply to message #228916] Thu, 22 January 2009 02:35 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
There is one more issue with paths. Perhaps it is not related directly to
the one reported in previous post.

So, I've got a makefile project for skyeye-1.2.5.
It is set up in the following way: project is created in the root of the
skyeye source tree (i.e. there is no linked folder to source code), build
location ${workspace_loc:/Skyeye_1.2.5}.

Here is the log

make[2]: Entering directory `/cygdrive/d/Dvs/Project/Skyeye_1.2.5/device'
gcc -DHAVE_CONFIG_H -DLCD -DWIN32_LCD -g -O0 -I. -I.. -I./ -I../arch/arm
-I../arch/arm/common -I../utils/config -I../utils/main -I../utils/main
-I../utils -I../device `pkg-config gtk+-2.0 --cflags` -MT
skyeye_lcd_win32.o -MD -MP -MF .deps/skyeye_lcd_win32.Tpo -c -o
skyeye_lcd_win32.o `test -f 'lcd/skyeye_lcd_win32.c' || echo
'./'`lcd/skyeye_lcd_win32.c
lcd/skyeye_lcd_win32.c: In function `skPenEvent':
lcd/skyeye_lcd_win32.c:94: error: `dflkgl' undeclared (first use in this
function)

As you can see, log produces relative paths. Moreover, make is recursively
called in few directories (in this case it is
'/cygdrive/d/Dvs/Project/Skyeye_1.2.5/device'. So the path
'lcd/skyeye_lcd_win32.c' is relative to
'/cygdrive/d/Dvs/Project/Skyeye_1.2.5/device'.

Here is what happens in ErrorParserManager.
fBaseDirectory is set to D:/Dvs/Project/Skyeye_1.2.5.
findFilePath() is called with filePath='lcd/skyeye_lcd_win32.c'
Since it is not absolute, at line 318 'path' is asigned with
'/cygdrive/d/Dvs/Project/Skyeye_1.2.5/device/lcd/skyeye_lcd_ win32.c' which
is correct Cygwin path to the file.
findFileInWorkspace() cannot find this file (line 325) and execution goes
to cygpath check.
cygpath converts filePath (which is relative 'lcd/skyeye_lcd_win32.c') to
'lcd\skyeye_lcd_win32.c'
Since fBaseDirectory is not a prefix of this path, 'path' is assigned to
'lcd/skyeye_lcd_win32.c' at line 339.
findFileInWorkspace() at line 341 returns a file with path
'/Skyeye_1.2.5/lcd/skyeye_lcd_win32.c' which is imaginary and is not
correct ('device' directory is absent).

Later is it coverted to canonical
D:\EclipseGanymedeSR1\lcd\skyeye_lcd_win32.c which is also wrong and this
process fails...

Dmitry
Re: Mapping error message path to Eclipse file [message #229189 is a reply to message #229173] Thu, 22 January 2009 04:30 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Cool! Thanks!

P.S. I would need to be more patient and read docs :-)
Re: Mapping error message path to Eclipse file [message #229197 is a reply to message #229181] Thu, 22 January 2009 10:42 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:
> lcd/skyeye_lcd_win32.c:94: error: `dflkgl' undeclared (first use in this
> function)

> As you can see, log produces relative paths.

Are you still using CDT 5.0.1? Can you try 6.0 build? I believe that the
issue with relative paths was fixed. It should scan all the files in your
project to find the file which rear matches (unless there are multiple
files like that).

> Here is what happens in ErrorParserManager.
> fBaseDirectory is set to D:/Dvs/Project/Skyeye_1.2.5.
> findFilePath() is called with filePath='lcd/skyeye_lcd_win32.c'
> Since it is not absolute, at line 318 'path' is asigned with
The file should be resolved long before that - in 6.0 version.

Andrew
Re: Mapping error message path to Eclipse file [message #229204 is a reply to message #229197] Thu, 22 January 2009 11:28 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Andrew Gvozdev wrote:
> Are you still using CDT 5.0.1?

Yes. It is release, so I will not move to intermediate version for daily
work

> Can you try 6.0 build?

Sure, I will.
Re: Mapping error message path to Eclipse file [message #229210 is a reply to message #229104] Thu, 22 January 2009 12:20 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Hi Axel
Axel Mueller wrote:

> I have a similar problem and no solution :-(.
> I am using the MS Visual C++ compiler on Linux with Wine. So I can compile
> for Linux (gcc) and Windows(msvc) on the same platform at the same time.
> The compiler output (cl.exe) uses, of course, Windows style path but
> Eclipse expects Linux paths. A path mapping from Wine to Linux would be
> very helpful to be able to click errors/warning in the Problem View.

Path mapping probably won't help you because Linux treats name like
"C:\src\Hello.cpp" as one continuous filename:

~/tmp$ touch "C:\\src\\Hello.cpp"
~/tmp$ ls -l
total 0 -rw-rw-r-- 1 ag dev 0 2009-01-22 12:15 C:\src\Hello.cpp

Andrew

> Axel
Re: Mapping error message path to Eclipse file [message #229218 is a reply to message #229204] Thu, 22 January 2009 12:32 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
>> Can you try 6.0 build?
> Sure, I will.

Well, it works for relative paths. That's great!

But it fails for paths like /usr/bla-bla-bla :

gcc -DHAVE_CONFIG_H -I. -I../.. -I./common -I../../utils/debugger
-I../../device/uart -I../../utils/config -I../../utils/main
-I../../utils/main -I../../utils -I../../device -MT ppc_vec.o -MD -MP
-MF .deps/ppc_vec.Tpo -c -o ppc_vec.o `test -f 'common/ppc_vec.c' || echo
'./'`common/ppc_vec.c
common/ppc_vec.c:32:1: warning: "log2" redefined
In file included from common/ppc_vec.c:26:
/usr/include/math.h:249:1: warning: this is the location of the previous
definition
Re: Mapping error message path to Eclipse file [message #229226 is a reply to message #229218] Thu, 22 January 2009 12:45 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

>>> Can you try 6.0 build?
>> Sure, I will.

> Well, it works for relative paths. That's great!

> But it fails for paths like /usr/bla-bla-bla :

> gcc -DHAVE_CONFIG_H -I. -I../.. -I./common -I../../utils/debugger
> -I../../device/uart -I../../utils/config -I../../utils/main
> -I../../utils/main -I../../utils -I../../device -MT ppc_vec.o -MD -MP
> -MF .deps/ppc_vec.Tpo -c -o ppc_vec.o `test -f 'common/ppc_vec.c' || echo
> './'`common/ppc_vec.c
> common/ppc_vec.c:32:1: warning: "log2" redefined
> In file included from common/ppc_vec.c:26:
> /usr/include/math.h:249:1: warning: this is the location of the previous
> definition
I assume this is cygwin path? Eclipse will consider C:\usr\include (if you
added it as a linked resource in your project).
Re: Mapping error message path to Eclipse file [message #229260 is a reply to message #229226] Fri, 23 January 2009 03:59 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Yes, it is Cygwing path. On my machine Cygwin is installed in
C:\Utils\Cygwin. There is no C:\usr\ on my machine.

CDT has detected Cygwin at the C:\Utils\Cygwin. My project contains
include path C:/Utils/Cygwin/usr/include (I suppose it was autodetected by
CDT for this toolchain)

cygpath return the following

d:\Dvs\Project> cygpath -w /usr/include/math.h
C:\Utils\Cygwin\usr\include\math.h
Re: Mapping error message path to Eclipse file [message #229530 is a reply to message #229260] Tue, 27 January 2009 10:05 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Andrew, should I report a bug for /usr/* issue?

Dmitry
Re: Mapping error message path to Eclipse file [message #229537 is a reply to message #229530] Tue, 27 January 2009 10:32 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

> Andrew, should I report a bug for /usr/* issue?

Can you add a comment to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261913 ?
I think it could be resolved in the scope of this task, after all "cygpath
-w /usr/bin" converts it to proper Windows path. I'll try to find some
time to look at this one. We have similar issue with absolute /usr/* paths
although not related to cygwin.

Andrew
Re: Mapping error message path to Eclipse file [message #229675 is a reply to message #228916] Wed, 28 January 2009 22:00 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Dmitry Smirnov wrote:

> I'm using Eclipse to debug QEMU simulator.
> When compiling this project, Cygwin produces error messages with path to
> file like

> /cygdrive/d/Dvs/Project/qemu-0.9.1/hw/omap.c:118: undefined reference to
> `ffs'
> These message are shown at the Problems view but not operable: I cannot go
> to source by clicking at the problem.
> Most likely, Eclipse/CDT cannot map /cygdrive/d/ to D:
> Is there any way to tell Eclipse how to do this?

You know, it appears that there *is* another way. Try right-click on the
problem in Problems view, then "Open external location". I am not sure
about markers, they show up in the opened file in some cases but in others
do not.

Andrew
Re: Mapping error message path to Eclipse file [message #229714 is a reply to message #229675] Thu, 29 January 2009 11:21 Go to previous messageGo to next message
Dmitry Smirnov is currently offline Dmitry Smirnov
Messages: 90
Registered: July 2009
Member
Andrew Gvozdev wrote:

> You know, it appears that there *is* another way. Try right-click on the
> problem in Problems view, then "Open external location". I am not sure
> about markers, they show up in the opened file in some cases but in others
> do not.

Great, this works. Even for /usr/include/math.h
The only point here is that files that are actually inside the project
(for instance, I have a compilation warning for common/exteption.c which
is actually located at path /Skyeye_1.2.5/arch/mips/common/exception.c)
are treated as external. At least they are marked with a "folder"
decoration of the icon (in the document title) and "Show In -> Project
Explorer" does not work.

Dmitry
Re: Mapping error message path to Eclipse file [message #229917 is a reply to message #229104] Tue, 03 February 2009 08:44 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Hi Axel,

Axel Mueller wrote:
> I have a similar problem and no solution :-(.
> I am using the MS Visual C++ compiler on Linux with Wine. So I can compile
> for Linux (gcc) and Windows(msvc) on the same platform at the same time.
> The compiler output (cl.exe) uses, of course, Windows style path but
> Eclipse expects Linux paths. A path mapping from Wine to Linux would be
> very helpful to be able to click errors/warning in the Problem View.

Can you provide some examples of output you are getting and what path
mapping you hope to get? Ideally in a form of bugzilla task. I am working
on more improvements in this area and would like to consider corner and
nut cases.

Andrew
Re: Mapping error message path to Eclipse file [message #230191 is a reply to message #229917] Fri, 06 February 2009 12:01 Go to previous messageGo to next message
Axel Mueller is currently offline Axel Mueller
Messages: 1926
Registered: July 2009
Senior Member
Compiler command:

cl -c -nologo -Zm200 -MD -O2 -O2 -Zc:forScope -GF
-FdY:/sources/HEAD/src_win32-msvc2005_release/obj/modultests /compilercap/
-DUNICODE -DWIN32 -DUSEDRIVE -DQT_THREAD_SUPPORT -DEFENCE_ON_DEBUG
-DNO_MEMDEBUG_RPT -DNDEBUG -DUSE_STOPWATCH -DQT_DLL -DQT_THREAD_SUPPORT
-DQT_NO_DEBUG -I"Y:\sources\HEAD\src_win32-msvc2005_release\gen"
-I" Y:\sources\HEAD\src_win32-msvc2005_release\gen\modultests\co mpilercap "
-I"c:\Qt\3.3.8\include" -I"Y:\sources\HEAD\src"
-I"Y:\sources\HEAD\src_win32-msvc2005_release" -I"." -I".."
-I"Y:\sources\HEAD\src\foreign\unittest++"
-I"Y:\sources\HEAD\src\common\base\baselib" -I"c:\Qt\3.3.8\include"
-I" Y:\sources\HEAD\src_win32-msvc2005_release\gen\modultests\co mpilercap "
-I" Y:\sources\HEAD\src_win32-msvc2005_release\gen\modultests\co mpilercap "
-I" Y:\sources\HEAD\src_win32-msvc2005_release\gen\modultests\co mpilercap "
-I"c:\Qt\3.3.8\mkspecs\win32-msvc2005"
-FoY:\sources\HEAD\src_win32-msvc2005_release\obj\modultests \compilercap\
@Y:\sources\HEAD\src_win32-msvc2005_release\tmp\nme8a4.tmp
fixme:file:NeedCurrentDirectoryForExePathW (L"cl"): partial stub
compcapc.c
\compcapc.c(43) : error C2065: 'paiOu' : undeclared identifier
\compcapc.c(43) : error C2109: subscript requires array or pointer type


Eclipse will show the two errors in the Problems View. But without any
Path.


Output from winepath:
winepath Y:/sources/HEAD/src/modultests/compilercap
/home/amueller/.wine/dosdevices/y:/sources/HEAD/src/modultes ts/compilercap

The files in /home/amueller/sources/HEAD/src/ are in the Eclipse workspace.

In principle, I would like to map Y:\ to /home/amueller

Axel


Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google
Re: Mapping error message path to Eclipse file [message #230199 is a reply to message #230191] Fri, 06 February 2009 12:32 Go to previous messageGo to next message
Andrew Gvozdev is currently offline Andrew Gvozdev
Messages: 253
Registered: July 2009
Senior Member
Thanks, this is helpful. Created
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263977

Andrew
Re: Mapping error message path to Eclipse file [message #230246 is a reply to message #230199] Mon, 09 February 2009 04:00 Go to previous message
Axel Mueller is currently offline Axel Mueller
Messages: 1926
Registered: July 2009
Senior Member
Andrew Gvozdev wrote:

> Thanks, this is helpful. Created
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=263977

> Andrew
Great. I added my email to the CC list. If you need any additional info or
help for testing please contact me.

Axel


Before you ask
- search this forum
- see the FAQ http://wiki.eclipse.org/CDT/User/FAQ
- google
Previous Topic:CDT 5.02
Next Topic:Unsatisfied dependincies with CDT 200901300802 (RC1) build.
Goto Forum:
  


Current Time: Wed Apr 16 00:50:55 EDT 2014

Powered by FUDForum. Page generated in 0.07801 seconds