Re: [linuxtools-dev] State of remote launch capability in linux tools

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

So, what parts of RDT would there be dependencies on?
Could these dependencies be optional?

I've seen the RDT Launcher mentioned... can you point me to the code, for reviewing it?

Also, you wrote
> .  I will post up this code in a bugzilla as an enhancement request, and example implementation.
Please CC me on that bug when you post it.

Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6


-----Original Message-----
From: linuxtools-dev-bounces@xxxxxxxxxxx [mailto:linuxtools-dev-bounces@xxxxxxxxxxx] On Behalf Of Corey Ashford
Sent: Tuesday, September 27, 2011 8:45 PM
To: Jeff Johnston; Linux Tools developer discussion
Subject: Re: [linuxtools-dev] State of remote launch capability in linux tools

On 09/27/2011 11:27 AM, Jeff Johnston wrote:
> On 09/26/2011 06:49 PM, Corey Ashford wrote:
>>
>> Hey folks,
>>
>> I'd like to understand where things are with regard to remote launch.
>>
>> We currently have a working remote launcher for Valgrind over PTP's 
>> RDT facility.  Our implementation essentially re-implements the 
>> org.eclipse.linuxtools.profiling.launch.remote.RemoteConnection 
>> package using RDT's API instead of RSE, and then uses the PTP Remote 
>> tab for configuring the remote connection.  To implement 
>> RemoteConnection and the launcher, I copied a number of protected 
>> methods from the PTP code, and used them in RemoteConnection and in 
>> the launch delegate.  I will post up this code in a bugzilla as an 
>> enhancement request, and example implementation.
>>
>> I am starting to work on a similar implementation for an OProfile 
>> remote launcher, and we may end up also doing similar things for 
>> remote gprof, and perf as well.
>>
>> However, I know that Jeff Johnston was/is exploring a different 
>> long-term strategy for remote launching, providing remote access, 
>> perhaps using another layer on top of RDT.
>>
>> Any news on this front?
>>
> 
> Still on-going.  It is a different scenario whereby we simply support 
> RDT projects with the same launcher/UI that's in place today.
> 
> So, an RDT project simply selects to run valgrind as a normal local 
> project would.  The setting up of the RDT connection, etc... has been 
> done in project creation.
> 
> The idea would be to have a common launcher under-the-covers much like 
> Autotools uses the CDT launcher today for its tool invocations and to 
> access files using RDT instead of directly.
> 

So should I infer from this that you've accepted that RDT is lightweight enough to create a dependency on it for Linux Tools launchers?

I like this idea, by the way.  Having a single launcher (per tool) would be easier for users to understand and use.

- Corey

_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev