| Indexer & Custom Builder Tools [message #138934] |
Tue, 15 February 2005 10:57  |
Eclipse User |
|
|
|
Originally posted by: alexfarberov.[nospam]hotmail.com
Hello,
I am working on a large project. There is a custom build utility that
replaces the standard make. The makefiles are completely different in
structure and have a different name than Makefile.
I can invoke the custom builder and it seems to work fine under CDT.
However, indexing does not work; I can't follow declarations or
references to files in other directories.
If I specify all the directories that contain header files in "Project
Properties | C++ Include Paths & Symbols", then the indexer runs for
days (literally) which is not acceptable given that for some reason it
seems to reindex the whole project on every change in the source.
Please let me know if there is an efficient way to use the indexer with
custom builders.
----
Platforms:
Solaris-Sparc 2.9, Sun CC 5.5
Linux Kernel 2.4.21-9.ELsmp, gcc version 3.2.3
Eclipse Version: 3.0.1
Build id: 200409161125
Eclipse C/C++ Development Tools Version: 2.1.0
Build id: 200412170841
Thanks,
Alex
|
|
|
|
| Re: Indexer & Custom Builder Tools [message #139248 is a reply to message #139179] |
Mon, 21 February 2005 10:48  |
| Eclipse User |
|
|
|
Originally posted by: alexfarberov.[nospam]hotmail.com
Thanks for the reply, John.
> We have an extension point that you can implement that
> you could use to register your build information (include paths &
> macros) as you see fit.
Could you please let me know where can I find further information
regarding registering my build information?
Thanks,
Alex
johnc wrote:
> Unfortunately, the current indexing strategy depends greatly upon correct
> build information. We have an extension point that you can implement that
> you could use to register your build information (include paths & macros) as
> you see fit.
>
> Changing just a single file should not cause the whole project to be
> reindexed unless that file is included in every piece of source. If you can
> provide us with an sample (toy) project that reproduces the scenario, I
> would suggest you raise a bug @ bugs.eclipse.org.
>
> JC
>
> "Alex Farberov" <alexfarberov@[nospam]hotmail.com> wrote in message
> news:cut654$rqh$1@www.eclipse.org...
>
>>Hello,
>>
>>I am working on a large project. There is a custom build utility that
>>replaces the standard make. The makefiles are completely different in
>>structure and have a different name than Makefile.
>>
>>I can invoke the custom builder and it seems to work fine under CDT.
>>
>>However, indexing does not work; I can't follow declarations or
>>references to files in other directories.
>>
>>If I specify all the directories that contain header files in "Project
>>Properties | C++ Include Paths & Symbols", then the indexer runs for
>>days (literally) which is not acceptable given that for some reason it
>>seems to reindex the whole project on every change in the source.
>>
>>Please let me know if there is an efficient way to use the indexer with
>>custom builders.
>>
>>----
>>Platforms:
>>Solaris-Sparc 2.9, Sun CC 5.5
>>Linux Kernel 2.4.21-9.ELsmp, gcc version 3.2.3
>>
>>Eclipse Version: 3.0.1
>>Build id: 200409161125
>>
>>Eclipse C/C++ Development Tools Version: 2.1.0
>>Build id: 200412170841
>>
>>
>>Thanks,
>>Alex
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05106 seconds
Home