Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] binary path in launch configs

Ah, that might work then. I'm going to go through and enable the CDT launches for the launchbar. I'll make the changes there since I want to get familiar with that code.

And yes, we can't guess it 100% every time. I was deliberately vague about the "hint" we'd have in the launch config. It could be the executable name which should be the same for all configs. Or we could store a different binary path for each mode. Something like that. Anyway we can work more on that as we get there. First I need to commit the latest and hopefully near final APIs for the launchbar. Then I'll look at the providers for CDT Local launches.

D


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
Sent: Thursday, July 10, 2014 7:07 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] binary path in launch configs

Good thing is there are no cdt changed needed if somebody wants to do it in their launch delegate, I just did for ours, 
if binary is not specified IDE will pick binary automatically during launch step.
The only weirdness for user - if they open this launch config it will have red mark "Binary is not specified".
Code is very generic - I can push this for cdt launch delegates if you want (but it won't be useful unless something creates binary-less launch configs)

To answer you question about if binary should be in LC - it has to because tool never can pick 100% correctly. Too many points of failure.


On Thu, Jul 10, 2014 at 4:26 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
Hey gang,

This has been the bane of our existence and it's about to get worse. One of the cool things with the launchbar is that it handles lots of different launch modes. Profiling is a good example. However the assumption is that one launch configuration can handle all these modes. But then, you're likely to want different build configurations to build with the right compiler options for these modes and that means you'll have to pick which binary to run with which mode. And then you add multiple target support and then...

The question is then, should the binary be in the launch configuration at all. Or should the delegate for the given mode, figure out which binary to use and then set the path as an attribute on the ILaunch? We could have hints in the launch configuration that the delegate can use, maybe the executable name, for example, and then the delegate can pick the right version of the executable based on it's needs.

Thoughts? I'd love to see CDT used for more than just run and debug and there's gnu toolchain support for more.
Thanks!
Doug.

_______________________________________________
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


Back to the top