| RE: [cdt-dev] Extending CDT |
|
The remote resources thing sounds very interesting but is beyond my current expertise so I will leave that alone…
You can very much customize the makefile generator in Managed Build. The extensibility document you refer to is rather out of date :-(
In CDT 2.0, in your toolchain definition you must specify a makefile generator via the target’s makefileGenerator attribute. This entry should point to a class which implements the IManagedBuilderMakefileGenerator interface. You can use the reference impelementation (org.eclipse.cdt.managedbuilder.makegen.gnu.GnuMakefileGenerator), or you can create your own. From there you can custom code your generator class to behave as you wish.
For more up to date documentation on the ManagedBuildInfo extension point, you are probably best off to refer to the documentation included with CDT. The way I usually get at it is to use the PDE to view the extension point description.
___________________________________________
Chris Recoskie Software Designer IDE Frameworks Group Texas Instruments, Toronto
-----Original Message-----
Hi,
I've just started looking at CDT and the possibility of extending it. My primary reason for extending CDT is to provide support for remote resources in eclipse. Eclipse only recognizes "local" projects and resources (files and folders). I have to support local (eclipse) projects (non CDT at this point) which contain remote resources accessed via a file transport system recognized by my project type. To leverage the rich C/C++ environment provided by CDT, I have to extend it to support remote resources. Since the remote host I am supporting is some flavour of unix/linux (the workstation is windows), I am hoping to be able to run a federated/distributed CDT environment by installing CDT (no GUI components) on the remote host and then implementing a "bridge" or a "connector" between the CDT on the workstation and the CDT running on the remote host. When a parse/scan/indexing is initiated on the workstation, the "bridge" or "connector" will relay the event to the "remote" CDT, trigger the same event on the remote host, collect the result, stream the result back to the workstation and somehow combine the results (workstation + remote). This will apply to content assist, outline view, build, search, etc. Is this something that is do-able in CDT 2.0 or 2.x eventually? I need to do this in the next few months.
I also want to take over the generation of the makefile in the managed build scenario. I have read the "Managed Build System Extensibility Document" and I understand that I can contribute my own tool chain, etc. But I want to take it one step further and generate the makefile as well... different format/syntax, to a remote host, of course.
Any comments will be appreciated.
Mary Huang
|