| 2 Questions about discovery options and #defines [message #172242] |
Fri, 07 July 2006 11:07  |
Eclipse User |
|
|
|
Originally posted by: jamesblackburn+ngnospam.gmail.com
Hi,
I am using Full Indexing and Discovery Options -> Per File Scanner
Profile, and would like to know if the following behaviour is normal for
Eclipse.
A few of the header files exist in multiple paths of the source tree.
Indexing and discovery have taken place, and, if I open the DOM AST view
on a file that links to one of the duplicate headers, the
#IASTPreprocessorIncludeStatement has the full path of the right header
file. However if I then double click on the header in Outline view,
Eclipse gives me a choice of which header to go to. Should it be doing
this given that it knows which header is correct?
Also is there any of getting Eclipse to know which #define's and
consequently which sections of code are enabled? I can't seem to figure
out how to get it to do this...
Cheers,
James
|
|
|
| Re: 2 Questions about discovery options and #defines [message #174165 is a reply to message #172242] |
Wed, 02 August 2006 05:54  |
| Eclipse User |
|
|
|
"JB" <jamesblackburn+ngnospam@gmail.com> wrote in message
news:e8ltbr$io1$1@utils.eclipse.org...
> Hi,
>
> I am using Full Indexing and Discovery Options -> Per File Scanner
> Profile, and would like to know if the following behaviour is normal for
> Eclipse.
>
> A few of the header files exist in multiple paths of the source tree.
> Indexing and discovery have taken place, and, if I open the DOM AST view
> on a file that links to one of the duplicate headers, the
> #IASTPreprocessorIncludeStatement has the full path of the right header
> file. However if I then double click on the header in Outline view,
> Eclipse gives me a choice of which header to go to. Should it be doing
> this given that it knows which header is correct?
You may want to raise a bug about this.
> Also is there any of getting Eclipse to know which #define's and
> consequently which sections of code are enabled? I can't seem to figure
> out how to get it to do this...
This is planned for 4.0
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=81511).
> Cheers,
>
> James
|
|
|
Powered by
FUDForum. Page generated in 0.03399 seconds
Home