I have a changelist in the works that should prevent ffmpeg_binaries from showing up. Andrew
On Sun, Jul 5, 2009 at 9:50 PM, Bradley Nelson <[email protected]>wrote: > In the case of cygwin and lastchange I think know what's going on, and > unfortunately these currently expect to always get built. > The cygwin case is so that setup_mount gets run before anything else and it > unfortunately wants to run every time. It's used to poke the registry to > prepare the quasi-hermetic cygwin for use. In the past this setup step was > just baked into most of the places that used it. By consolidating it, the > script gets run only once at the beginning of each build. At one point the > issue was that rules files caused this to be needed per IDL file, but since > that got moved to a generated makefile, it can probably be done as it was > before. I'm willing to find a way to make it work like before if anyone > chimes in with a strong preference (beng?). > > lastchange is related to asking svn for change information to generate a > version number. Since MSVS doesn't know anything about svn it can't know > when to rebuild. In the past this was basically handled incorrectly (it > would run once per checkout). Which meant svn changes would not get > detected. Since we do clean checkouts for real releases, it's probably moot. > Again if anyone feels strongly, we can put it back the way it was before. > > With ffmpeg_binaries, a casual look suggested its just a mistake in how the > action is setup, and can be fixed. I'll look into this tomorrow. > > -BradN > > > > On Sun, Jul 5, 2009 at 1:00 PM, Thiago Farina <[email protected]>wrote: > >> >> In my machine cygwin, ffmpeg_binaries, lastchange are always built >> when I click in F5 to start debugging chromium. But they don't take >> too long to be built. >> >> On Jul 5, 4:50 pm, Finnur Thorarinsson <[email protected]> wrote: >> > Oh, right. When I look at the list of projects (from your email) again I >> > realize that cygwin and lastchange are always built on my machine as >> well, >> > but they take very little time to build. I don't see any ffmpeg projects >> > getting built, though, and it certainly doesn't take a minute to build a >> > small change, but then again I have a reasonably speedy machine. >> > What project is taking a minute to build and what kind of hardware are >> you >> > building on? Also, have you looked at the tips page on speeding up the >> > build? I'd look it up for you, but I need to run... >> > >> > >> > >> > On Sun, Jul 5, 2009 at 12:37, tux316 <[email protected]> wrote: >> > > Those projects have their own custom build steps. So Visual Studio >> will >> > > always think that they are out of date, because those steps need to be >> > > called first. I am pretty sure this is normal, since it also happens >> with >> > > me and I use Visual Studio 2008. >> > >> > > Hope that helps. >> > >> > > - >> > >> > > Juan Baez >> > >> > > *From:* [email protected] [mailto: >> > > [email protected]] *On Behalf Of *Finnur Thorarinsson >> > > *Sent:* Sunday, July 05, 2009 11:32 AM >> > > *To:* [email protected] >> > > *Cc:* Chromium-dev >> > > *Subject:* [chromium-dev] Re: Some projects are always out of date >> > >> > > Yeah, I've had this happen a few times -- not these projects >> specifically, >> > > but for example when Visual Studio wants to build Webcore every time I >> make >> > > a change in the browser project. Most annoying, but usually it goes >> away if >> > > I rebuild. >> > >> > > I would therefore suggest gclient sync and rebuild all. It will take >> some >> > > time, of course, so plan accordingly. :) >> > >> > > On Fri, Jul 3, 2009 at 20:10, Hua <[email protected]> wrote: >> > >> > > Hi, >> > > Every time I hit F5 in VS2005, it will pop up a dialog say: >> > >> > > These projects are out of date: >> > > cygwin - Debug Win32 >> > > ffmpeg_binaries - Debug Win32 >> > > lastchange - Debug Win32 >> > > Would you like to build them? >> > > ... >> > >> > > If I choose to build them, they will be built in a minute or so and >> > > then Chrome runs. But next time I hit F5 again (without any code >> > > changes), the same dialog will be shown again. >> > >> > > Anyone else run into this? >> > >> > > -- >> > > Hua >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
