Re: [cdt-dev] debug - active build configuration changes during launch

["James Blackburn" <jamesblackburn@xxxxxxxxx>]

On Wed, Oct 29, 2008 at 1:38 PM, Elena Laskavaia <elaskavaia@xxxxxxx> wrote:
> Here is my 2 cents. We can add another launch constant (property?), lets say
>
>        public static final String ATTR_PROJECT_BUILD_CONFIG_BEHAVIOR =
> CDT_LAUNCH_ID + ".PROJECT_BUILD_CONFIG_BEHAVIOR";
>
> which has values:
> NO_BUILD - no build for this launch at all
> USE_BUILD_ID - use build it set using ATTR_PROJECT_BUILD_CONFIG_ID to do
> build
> USE_ACTIVE - use active build to do a build
>
> (last two only applicable if build when launch is enabled)
>
> Default value can be USE_BUILD_ID which is current, or USE_ACTIVE is less
> buggy. This approach would not require adding extra UI in 5.0.2.

Surely the original intention of this feature is to ensure that the
binary is up-to-date by building the configuration which produced the
binary.  Perhaps a better way of solving the problem might be a
boolean attribute ATTR_PROJECT_BUILD_ASSOCIATED_CONFIG  and a method
on the build system to find the configuration associated with the
binary?

Cheers,

James

>
>
> Ken Ryall wrote:
>>
>> I'm not completely sure but I think the first thing I'll do is add a
>> setting
>> so you can disable this feature completely. Then I'll work on the other
>> issues you mentioned.
>>
>> - Ken
>>
>>> From: ext Elena Laskavaia <elaskavaia@xxxxxxx>
>>> Organization: QNX
>>> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>> Date: Tue, 28 Oct 2008 17:20:11 -0400
>>> To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>> Subject: Re: [cdt-dev] debug - active build configuration changes during
>>> launch
>>>
>>> Please describe how do you propose fixing it for 5.0.2?
>>>
>>> Ken Ryall wrote:
>>>>
>>>> Elena,
>>>>
>>>> I worked on this originally and I agree that it needs to be improved to
>>>> handle the problems and use cases you mentioned. Please don't remove it.
>>>> I'll work on some short term improvements for 5.0.2 and more for 6.0.
>>>>
>>>> - Ken
>>>>
>>>>> From: ext Elena Laskavaia <elaskavaia@xxxxxxx>
>>>>> Organization: QNX
>>>>> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>>>> Date: Tue, 28 Oct 2008 16:48:34 -0400
>>>>> To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
>>>>> Subject: [cdt-dev] debug - active build configuration changes during
>>>>> launch
>>>>>
>>>>> Regarding
>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=229740
>>>>>
>>>>> We have a "feature" that launch config remembers first active launch
>>>>> configuration for managed projects and when
>>>>> it launches (if build when launch enabled) it is setting it to active
>>>>> and
>>>>> then
>>>>> builds.
>>>>>
>>>>> This is really bad, because
>>>>> a) It does not restore active build config that was set by user,
>>>>> meaning my
>>>>> active config magically changes for unknown reason (I know why now...)
>>>>> b) If user changes project in launch config this magical build config
>>>>> does
>>>>> not
>>>>> change, so if you lucky you have same launch config in this another
>>>>> project
>>>>> and
>>>>> it will build, if not you get an NPE (bug236847 which is fixed on trunk
>>>>> by
>>>>> somebody)
>>>>> c) If user deletes related config same NPE
>>>>> d) There is no user setting that allow to change or even view config
>>>>> associated with the launch
>>>>> e) additionally if project is not managed project or not intent to be
>>>>> re-build
>>>>> when launching there is no way to specify it
>>>>>
>>>>> I will remove this functionality in 5.0.2 (i.e. setting active config
>>>>> to
>>>>> "launch" related build config when building, it will build user
>>>>> selected
>>>>> active config).
>>>>> any objections?
>>>>>
>>>>> For 6.0 we should implement proper fix:
>>>>> - support from UI
>>>>> - support when build config is deleted
>>>>> - support if different project is selected
>>>>> - support for "none" as build config - that allow not to build project
>>>>> for
>>>>> this launch
>>>>> _______________________________________________
>>>>> 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
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>