[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cdt-dev] Handling complex remote launch/debug scenarios?
- From: Joseph Green <jgreen@xxxxxxxxxx>
- Date: Wed, 7 Dec 2011 09:58:17 -0800
- Delivered-to: firstname.lastname@example.org
On 12/5/11, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx> wrote:
> Don't think there's a solution out there right now, but it sure would be
> nice. Even if it was a list box where we can specify which files to download
> (as opposed to the single binary).
Is this something we should expand beyond just download support? What
about having the ability to manage a list of make targets, and having
any target or source file have an installed path, permissions,
ownership? Then we could have builders for things like RPM, BitBake
or Windows installers use this information to do packaging.
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Anna Dushistova
>> Sent: Monday, December 05, 2011 12:49 PM
>> To: cdt-dev@xxxxxxxxxxx
>> Subject: [cdt-dev] Handling complex remote launch/debug scenarios?
>> Hi All,
>> In CDT we provide the UI to download/install just the binary we are going
>> debug but not its dependencies be they in the same project or in the
>> referenced projects. It would be nice to have some UI to help users in
>> situations, however, I am not quite sure what the design should be. Does
>> anyone has an idea?
>> Or am I missing something and there is a solution for my problem already?
>> cdt-dev mailing list
> cdt-dev mailing list