[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [Dltk-dev] Triggering script builds
|
Probably you should report your changes as structural.
Structural here means "change of the external module interface".
The idea is simple if you change external interface, like add/remove
class member, then all the dependent modules should be recompiled, but
if change was completely internal, like 1->2 in the body of the
function - then it's not necessary to recompiled other files.
On Sat, Sep 24, 2011 at 00:18, Timothy Wall wrote:
> Thanks. Set that up, extracted the dependencies from built models, and fed them into IBuildState.
>
> The dependencies are being saved in a queue, but subsequent builds are not triggered. In this statement in ScriptBuilder.java:555,
>
> while (!buildState.getStructuralChanges().isEmpty()
> && !queue.isEmpty()) {
>
> since the structural changes map is empty (the queue is non-empty), the queue is never read (builders are again called in the body of this loop) - perhaps the test should be an OR instead of AND?
>
>
> On Sep 23, 2011, at 11:55 AM, Alexey Panchenko wrote:
>
>> Hi Timothy,
>>
>> 1. create IScriptBuilder implementation and contribute it via extension point
>> 2. in build() function report dependencies via
>> IBuildState.recordDependency(main, included)
>>
>> Regards,
>> Alex
>>
>> On Fri, Sep 23, 2011 at 17:38, Timothy Wall <twall@xxxxxxxxxxxx> wrote:
>>> BTW, the trigger needs to be added dynamically as the user edits the list of includes.
>>>
>>> On Sep 23, 2011, at 10:58 AM, Timothy Wall wrote:
>>>
>>>> I'd like to trigger a re-build of my script when one of its imports/includes changes.
>>>>
>>>> Is there any existing API (either in DLTK or eclipse proper) to add such a trigger?
>>>>
>>>
>>> _______________________________________________
>>> dltk-dev mailing list
>>> dltk-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>>>
>> _______________________________________________
>> dltk-dev mailing list
>> dltk-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
> _______________________________________________
> dltk-dev mailing list
> dltk-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dltk-dev
>
