Eclipse Community Forums: C / C++ IDE (CDT)

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » CDT extension points

Show: Today's Messages :: Show Polls :: Message Navigator

CDT extension points [message #118665]

Wed, 01 September 2004 18:43

Terry Chan

Messages: 9
Registered: July 2009

Junior Member

Hello,
I've been looking at the CDT SDK and trying to figure out what all the CDT
extension points do. Some I'm able to figure out simply by looking at the
source code and various manifest files, but there're still some that are
less obvious to me. Here are some of the extension points that I don't
know the purpose of:

org.eclipse.cdt.core.ScannerInfoProvider
org.eclipse.cdt.core.PathEntryContainerInitializer
org.eclipse.cdt.make.core.ExternalScannerInfoProvider
org.eclipse.cdt.core.ManagedBuildTools

What do these extension points do? Are they meant to be exploited by tool
vendors who want to extend CDT with their development tools? Or are they
meant strictly for CDT's internal usage?

thank you.
Terry

Report message to a moderator

Re: CDT extension points [message #118705 is a reply to message #118665]

Wed, 01 September 2004 19:24

Sean Evoy

Messages: 195
Registered: July 2009

Senior Member

Terry,
Here is the 10000 foot view:

ScannerInfoProvider is deprecated and no longer used.

PathEntryContainerInitializer allows plugin developers to register a
class that will populate the values of a PathEntryContainer (a feature
used to store defined symbols, includes paths, source directories, etc).

ExternalScannerInfoProvider allows you to register a class that figures
out what includes paths and symbols a compiler is using (so internal CDT
features function more efficiently).

There's a whole article dedicated to the ManagedBuildTools, but
essentially it is the point you extend to add a custom toolchain.

Sean

Terry Chan wrote:

> Hello,
> I've been looking at the CDT SDK and trying to figure out what all the CDT
> extension points do. Some I'm able to figure out simply by looking at the
> source code and various manifest files, but there're still some that are
> less obvious to me. Here are some of the extension points that I don't
> know the purpose of:
>
> org.eclipse.cdt.core.ScannerInfoProvider
> org.eclipse.cdt.core.PathEntryContainerInitializer
> org.eclipse.cdt.make.core.ExternalScannerInfoProvider
> org.eclipse.cdt.core.ManagedBuildTools
>
> What do these extension points do? Are they meant to be exploited by tool
> vendors who want to extend CDT with their development tools? Or are they
> meant strictly for CDT's internal usage?
>
> thank you.
> Terry
>

Report message to a moderator

Previous Topic:	Code navigation for reverse engineering C code question
Next Topic:	Pbarray.cpp not compiling

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Feb 05 14:01:34 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter