Re: [cdt-dev] cdt, windows, and tools

[Jeff Johnston <jjohnstn@xxxxxxxxxx>]

Sorry, I should have commented earlier.

Autotools remote support was originally added for PTP support.  If you look at the history of RemoteCommandLauncher,

you will see that Autotools support was originally added as part of:

Bug 430831 - add autotools support for PTP synchronized project

This originally supported PTP remote projects or local projects.

When I added initial Container build support, I modified RemoteCommandLauncher to use the CommandLauncherManager if not running remotely to

determine the default ICommandLauncher.  Autotools requested the RemoteCommandLauncher and this would end up figuring out the right ICommandLauncher to use.

Any testing of the remote Autotools support would be in PTP.

- Jeff J.

On Thu, Apr 19, 2018 at 4:14 PM, Scott Lewis <scottslewis@xxxxxxxxx> wrote:

On 4/11/2018 9:00 AM, Scott Lewis wrote:

Thanks for the info.

In autotools specifically, I've noticed the use of org.eclipse.remote API.   Two questions about the use of org.eclipse.remote:

1) Was it built in to some/all of the other toolchains?
2) Has it been tested/used for (e.g.) * -> linux remoting...with autotools specifically?   If it has been tested or used under such conditions, is there any code available as part of CDT or elsewhere?

Should I interpret the lack of response to this question as indicating that there are no actual impls/uses of org.eclipse.remote that have been tested with autotools?

Thanks,

Scott

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev