[webkit-dev] Compiling WebKit up to 25% faster in Windows?
dpranke at chromium.org
Tue Mar 26 13:46:50 PDT 2013
On Tue, Mar 26, 2013 at 1:42 PM, Alexis Menard <alexis at webkit.org> wrote:
> On Tue, Mar 26, 2013 at 5:40 PM, Dirk Pranke <dpranke at chromium.org> wrote:
> > On Tue, Mar 26, 2013 at 1:29 PM, Benjamin Poulain <benjamin at webkit.org>
> > wrote:
> >> On Tue, Mar 26, 2013 at 1:20 PM, Dirk Pranke <dpranke at chromium.org>
> >>> If we have consensus that we should just switch to paths relative to
> >>> Source (or maybe a couple different options), that would be (IMO) a
> big win.
> >>> It sounds like Daniel & co. have already done the big bang conversion.
> >> I think using full path would be a serious hit regarding hackability.
> >> I would rather spend some time tweaking my compiler to cache each
> >> directory content than waste time finding where is every single header I
> >> need to include.
> > Interesting. I have the exact opposite experience, having to paw around
> > figure out where "Font.h" actually lives rather than just seeing
> > "WebCore/platform/graphics/Font.h".
> But a modern IDE can easily solve that for you. You just click on the
> header and it opens it for you. Xcode, QtCreator handles it very well.
> That said if you don't use an IDE then I understand your point :).
I think to me the fact that the paths are spelled out is both one less
action I have to do to get my question answered (I don't have to click),
and a helpful reminder of the general layout of the code (and which
directories I might need to care about in relation to a particular file).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev