Skip to main content

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

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.

Back to the top