[webkit-help] Testing modifications to Webkit efficiently

[Lay Kuan Loh]

Thank you Konstantin and Gyuyoung. That helped me debug more quickly.



On Sun, Jul 24, 2016 at 11:09 PM, Gyuyoung Kim <gyuyoung.kim at webkit.org>
wrote:

> >> From reading the documentation on using WebKit, it seems that I need to
> build the entire codebase by running build-webkit each time I want to test
> a new change I made. Given that it takes about 90 min to run the build on
> my laptop, this seems like an inefficient way of developing webkit.
>
> >Incremental rebuilds usually take much less time.
>
> If you're using WebKit GTK port, there are some tips to speed up build
> time.
>
> - https://trac.webkit.org/wiki/WebKitGTK/SpeedUpBuild
>
> gyuyoung.
>
> On Mon, Jul 25, 2016 at 5:39 AM, Konstantin Tokarev <annulen at yandex.ru>
> wrote:
>
>>
>>
>> 24.07.2016, 23:08, "Lay Kuan Loh" <lloh at andrew.cmu.edu>:
>> > Hi all,
>> >
>> > Newcomer to webkit here.
>>
>> You're welcome :)
>>
>> >
>> > I am trying to modify WebKit for my own purposes. I do not plan to ship
>> my modifications to the official codebase.
>>
>> If you accidentally make (whatever small) improvements which can be
>> useful for other WebKit users, please consider upstreaming them. Every
>> little piece counts.
>>
>> >
>> > How would I check that the changes I make to WebKit did not break
>> anything? For instance, I am making changes to the
>> file WebKit/Source/WebCore/dom/Element.cpp and would like to test them
>> incrementally.
>>
>> You need to run Layout Tests. Read articles from
>> https://trac.webkit.org/wiki#LayoutTests
>>
>> You don't need to run all tests at once, run-webkit-tests allows you to
>> specify directory or individual test files.
>>
>> >
>> > From reading the documentation on using WebKit, it seems that I need to
>> build the entire codebase by running build-webkit each time I want to test
>> a new change I made. Given that it takes about 90 min to run the build on
>> my laptop, this seems like an inefficient way of developing webkit.
>>
>> Incremental rebuilds usually take much less time.
>>
>> >
>> > I am trying to modify WebKit for my own purposes. I do not plan to ship
>> my modifications to the official codebase.
>> >
>> > How would I check that the changes I make to WebKit did not break
>> anything? For instance, I am making changes to the
>> file WebKit/Source/WebCore/dom/Element.cpp and would like to test them
>> incrementally.
>> >
>> > From reading the documentation on using WebKit, it seems that I need to
>> build the entire codebase by running build-webkit each time I want to test
>> a new change I made. Given that it takes about 90 min to run the build on
>> my laptop, this seems like an inefficient way of developing webkit.
>> >
>> > Am I missing something obvious, on how to speed up testing my changes
>> to WebKit? I've googled around but for some reason can't find any clear
>> instructions on doing this.
>> >
>> > I've also posted the same question to stack overflow here.
>> >
>> > Thanks!
>> > ,
>> >
>> > _______________________________________________
>> > webkit-help mailing list
>> > webkit-help at lists.webkit.org
>> > https://lists.webkit.org/mailman/listinfo/webkit-help
>>
>>
>> --
>> Regards,
>> Konstantin
>> _______________________________________________
>> webkit-help mailing list
>> webkit-help at lists.webkit.org
>> https://lists.webkit.org/mailman/listinfo/webkit-help
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-help/attachments/20160724/e78279e2/attachment.html>