Re: [webkit-dev] Fwd: Compiling WebKit up to 25% faster in Windows?
On Mar 26, 2013, at 9:56 PM, Brent Fulgham bfulg...@gmail.com wrote: Hi, On Mar 26, 2013, at 1:50 PM, Ryosuke Niwa rn...@webkit.org wrote: Interesting. I have the exact opposite experience, having to paw around to figure out where Font.h actually lives rather than just seeing WebCore/platform/graphics/Font.h. On TextMate or Xcode, all I need need to is to type in Font.h and they'll automatically find the right file for me. I'll be annoyed if people started using same filenames in multiple directories (this has already happened :( ) because then various tools will start listing multiple files from all those directories. This can be a problem for implementation files, too, at least under windows. Can I share the joy of tracking down linker errors due to multiple compilation units with the name Foo.obj :) That said, I really do prefer the segmented include paths for the same reasons Dirk shared. I also would prefer full paths even if I still had to unique-ify the names themselves. But I'd prefer not to have to unique-ify the names; it's awkward for me. Thanks, -Brent ___ 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
[webkit-dev] Fwd: Compiling WebKit up to 25% faster in Windows?
Resent from the right email address. On Tue, Mar 26, 2013 at 1:40 PM, Dirk Pranke dpra...@chromium.org wrote: On Tue, Mar 26, 2013 at 1:29 PM, Benjamin Poulain benja...@webkit.orgwrote: On Tue, Mar 26, 2013 at 1:20 PM, Dirk Pranke dpra...@chromium.org wrote 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 to figure out where Font.h actually lives rather than just seeing WebCore/platform/graphics/Font.h. On TextMate or Xcode, all I need need to is to type in Font.h and they'll automatically find the right file for me. I'll be annoyed if people started using same filenames in multiple directories (this has already happened :( ) because then various tools will start listing multiple files from all those directories. - R. Niwa ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Fwd: Compiling WebKit up to 25% faster in Windows?
Hi, On Mar 26, 2013, at 1:50 PM, Ryosuke Niwa rn...@webkit.org wrote: Interesting. I have the exact opposite experience, having to paw around to figure out where Font.h actually lives rather than just seeing WebCore/platform/graphics/Font.h. On TextMate or Xcode, all I need need to is to type in Font.h and they'll automatically find the right file for me. I'll be annoyed if people started using same filenames in multiple directories (this has already happened :( ) because then various tools will start listing multiple files from all those directories. This can be a problem for implementation files, too, at least under windows. Can I share the joy of tracking down linker errors due to multiple compilation units with the name Foo.obj :) That said, I really do prefer the segmented include paths for the same reasons Dirk shared. Thanks, -Brent ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
