Re: [linuxtools-dev] PTP/RDT and remote linuxtools

[Greg Watson <g.watson@xxxxxxxxxxxx>]

On Oct 14, 2011, at 9:02 PM, Corey Ashford wrote:

> 
>> If RDT already has a Makefile builder and scanner discovery etc..,
> 
> It doesn't have a Makefile builder (yet), but it does have scanner discovery.

As far as I know there is are remote builders for both managed and unmanaged projects that are used by both remote projects and synchronized projects.

> 
>> perhaps an alternative would be to hook these up on the fly when we
>> recognize the situation. Otherwise, we will have to have a special
>> project wizard. I prefer the idea of just using the filesystem combo box
>> to determine where the project resides and thereby leaving all other UI
>> elements the same as well as having common code for local and remote.
>> 
>> Any thoughts?
> 
> The combo box seems clear enough.
> 
> It's not clear to me why the PTP/RDT developers chose to use a separate project type "Remote C/C++ project" and introducing a different mechanism for choosing toolchains, instead of reusing the C/C++ project type.  Maybe Greg Watson can fill us in here...

With the current CDT design,  the only wa to configure the remote aspects of the project, as well as add a remote nature to the project, is by adding a new project type. Since toolchains are linked to the project type, this means that remote version of the toolchains are also required.

Note that I recently added a new interface to PTP that simplifies obtaining the location of resources. The normal getLocationURI() will return the URI of the resource on the remote system for remote projects, but will return the local URI for synchronized projects. This new interface lets an IResource be adapted to an IRemoteResource which provides a single method for obtaining the remote location of the resource regardless of the project type. It will be available in PTP 6.0.

Regards,
Greg