Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] No correlation between build and run configurations

I think Ken has implemented and committed his changes to HEAD. He
added a a pop-up menu to the Main tab to let you select the build
configuration you wanted to tie the launch to.  As I commented in:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=229740 comment 5
I don't see why such an addition is necessary.

If the user is debugging "Debug/helloworld" then they want the build
configuration which outputs to "Debug"  to be built.  I don't see why
they should have to configure this.  Surely there Launch could query
(via some magic which may or may not exist) to discover this...?  This
wouldn't work for standard makefile projects, but then I haven't seen
a way to tie a make target to a project configuration build.

James

2009/2/19 Elena Laskavaia <elaskavaia@xxxxxxx>:
> 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
>


Back to the top