Re: [webkit-dev] Fwd: Compiling WebKit up to 25% faster in Windows?

2013-03-27 Thread Filip Pizlo

On Mar 26, 2013, at 9:56 PM, Brent Fulgham  wrote:

> Hi,
> 
> On Mar 26, 2013, at 1:50 PM, Ryosuke Niwa  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


Re: [webkit-dev] Fwd: Compiling WebKit up to 25% faster in Windows?

2013-03-26 Thread Brent Fulgham
Hi,

On Mar 26, 2013, at 1:50 PM, Ryosuke Niwa  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