Re: [cdt-dev] No correlation between build and run configurations

[<ken.ryall@xxxxxxxxx>]

Title: Re: [cdt-dev] No correlation between build and run configurations

This is bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=229740

Fixed in HEAD.

---

From: ext Elena Laskavaia <elaskavaia@xxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Thu, 19 Feb 2009 19:12:50 +0100
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] No correlation between build and run configurations

Actually there is, which creates more problem then solves.
Launch configuration keep invisible reference to active build configuration in which
it was created and tries to re-build that. I was proposing to make it visible. Ken suppose to work on that I have not heard anything from him since.

Mike Wrighton wrote:
> I've had some complaints about build/run configurations in CDT and
> after some thought, raised the following bug into our internal bug
> tracker. I thought the best way to ask this question was to copy the
> text from my bug into this mail!
>
> Cheers,
> Mike
>
>
>
> Bug:
> *** No correlation between build and run configurations ***
>
> There is no link inside CDT between build and run configurations. This means
> that if you attempt to launch a run configuration, the binary that will be
> rebuilt (if needed) corresponds only to the active build configuration, which
> may be different from that which generated the binary you wish to run.
>
> For example, you may have 2 binaries, debug and release. A run configuration
> may point to the debug binary, whilst the current active build configuration is
> set to release. When that run configuration is launched and the source has
> changed, the release binary, rather than the debug binary will be rebuilt.
>
> Currently the launch configuration only stores the path to the binary to be run
> (presumably since this could be an externally built binary). Some correlation
> between the configuration which built the binary, and the run config is needed.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev