On Fri, Nov 14, 2008 at 1:12 AM, Steven Knight <[EMAIL PROTECTED]> wrote:
> > - There are a couple of different ways we're (still) considering > handling bootstrapping the generated solution files. Right now, the best > bet looks to be checking in a stub solution file with a single target in a > project that generates the real solution+project files. Other > possibilities > include extending gclient to generate them after an update (which might be > the mechanism for keeping working copies in sync without manual steps, > anyway). > > As I did in the initial thread about this, I +1 the idea of extending gclient, or pretty much any other solution than checking in stubs (or non-stubs). > > - The Linux team have been having some performance issues, mostly > related to the long lists of -I directories used by Webkit. I intend to > have optimizations in place before launch. (This might be a blocking item, > depending on measurements on Windows.) > > May be worth bringing up with WebKit folks some time as a question about whether they'd take a patch to change all their #includes to have paths and then reduce the number of include paths. I can't believe it wouldn't also speed up VS, XCode, etc. build times. Darin says we can't compile a single source file. I use ctrl-f7 all the time in VS. Is there any way to support this or is it totally infeasible? PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
