On Sun, 4 Jan 2009, Brett Wilson wrote: > > On Sun, Jan 4, 2009 at 1:23 PM, Darin Fisher <[email protected]> wrote: > > This problem could also be solved by ignoring DerivedSources.make, and > > instead just add the "source" files to the vcproj. Then write a custom > > .rules file for each file type that runs the appropriate batch command to > > create the generated file. Then, dependency tracking would work just as it > > does for .cpp files. > > Well, but you'd still have the slowness of spawing perl hundreds of > times. I'm not sure that would speed up the build at all (though it > would improve the dependency management).
But you would only pay it once. Using native vcproj files may get the dependencies right and maybe you wouldn't need to do a full rebuild after each sync then. Or maybe I put too much faith in MSVC's dependency management. > > Our DerivedSources.make is already so tremendously out of sync with the one > > upstream that there doesn't seem to be much point in using it. > > I agree. It's not used in the scons build which properly tracks dependencies so the files are only generated once. Would Incredibuild be able to parallelize the perl scripts or does it only know how to parallelize c++ compiles? --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
