On Tue, Mar 26, 2013 at 2:37 PM, Ryosuke Niwa <rn...@webkit.org> wrote:
> On Tue, Mar 26, 2013 at 11:21 AM, Daniel Bratell <brat...@opera.com>wrote: > >> Is this something that has been talked about in the past, and would you >> be interested in replacing the long list of directories to search for every >> include with paths (relative some good base) directly in the include >> directives? >> > > Using explicit paths to include files has been talked about in the past; > e.g. > https://lists.webkit.org/pipermail/webkit-dev/2011-November/018632.html > > The most convincing counter argument I can remember is that it'll make > refactoring harder because you'll have to update all #include's when you > move headers. > A few tailored scripts make that an easier job. We're all engineers after all. > > It would be great if we can figure out if this also improves the build > time on Mac/Linux. > Agreed. Somewhat apples and oranges of course, but the noticeable slow down when compiling WebKit versus the rest of Chromium, file to file, is enormous. Chromium does a full path include directive from the base of the src by convention. I'd love to see Windows builds sped up; definitely the biggest pain point in continuous integration. > > - R. Niwa > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
