Re: [cdt-dev] Extending CDT

["Mary Huang" <mary.huang@xxxxxxxxxxx>]

We currently have a tcp/ip based framework for accessing these remote files
and for remote execution of commands. All the files reside on the remote
host and are only replicated/cached locally for editing purposes. All
tools/commands are run on the remote host where these files reside. Eclipse
is not really "aware" of these remote files... in other words, CDT will not
really "see" these files locally. My team has gone to much lengths writing
plugins that provides this framework and a project environment in eclipse
such that end-users can enjoy working with their remote files in the (local)
eclipse environment on their workstation. Now, we have to figure out how to
fit CDT into the picture and work with this non-traditionaly eclipse project
and resources. The option I'm looking into is the federated/distributed CDT
environment.


----- Original Message ----- 
From: "Johan Walles" <walles@xxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Sent: Tuesday, July 06, 2004 3:05 PM
Subject: Re: [cdt-dev] Extending CDT


> Why not just access the remote files using some Java implementation of
> the ssh protocol?
>
>    //Johan
>
> Mary Huang wrote:
> > 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
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev