Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-core-dev] [conflicting names] problem

My 2 cents in this regard.
 
I had raised a request to HP aCC team so that they start emitting the
compilation path as full path instead of relative path.
ie.,instead of emitting "../src/path1/file.h", gcc can say
"/home/cdt/something/src/path1/file.h" in its compilation messages.
 
The moment this feature was implemented, then the conflicting names problem
will be automatically resolved. 
This can be an optional feature in gcc by setting some user_defined_options
so that we don't break the existing functionality of the gcc.
 
We can make a similar request to gcc also so that this problem gets resolved
in a cleaner fashion. I had updated the same information in the bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=108489
 
Thanks,
Bala 
Hewlett-Packard.

________________________________

From: cdt-core-dev-bounces@xxxxxxxxxxx
[mailto:cdt-core-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett, Norbert
Sent: Monday, February 13, 2006 12:36 PM
To: CDT Core developers list.
Subject: AW: [cdt-core-dev] [conflicting names] problem


Michael,
 
the problem is known to us -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=108489
So far nobody has volunteered to fix it :-(
 
 
Norbert Ploett

________________________________

Von: cdt-core-dev-bounces@xxxxxxxxxxx
[mailto:cdt-core-dev-bounces@xxxxxxxxxxx] Im Auftrag von LAMB, Michael
Gesendet: Freitag, 10. Februar 2006 00:08
An: cdt-core-dev@xxxxxxxxxxx
Betreff: [cdt-core-dev] [conflicting names] problem



Good morning all,

The error parser seems to flag an error/warning as [conflicting names] if
the error occurred in a file name that also exists in another directory. It
doesn't seem to use the path - only the name - in determining if the name is
conflicted or not.

This creates problems in the cross-platform programs that I work on where we
have both a linux and win32 directory in a standard make project. Each of
these directories for example contain a udp.h/upd.cpp set of files and the
makefile for each platform decides which directory to use. The error parser
won't display problem markers in these files due to the problem that I
described above.

Is this a deliberate decision to only allow one instance of a file name
throughout a whole project?

Thank you,

Michael Lamb





Back to the top