Hmm... chrome_dll.vcproj has a special rules file that is supposed to cause chrome_dll.rc to be rebuilt whenever chrome/VERSION changes. It worked last I checked, but perhaps there is a bug now. Hopefully it is helpful to you to know where to find the relevant build files. Good luck. -Darin
On Fri, Sep 26, 2008 at 12:00 AM, Wei Hu <[EMAIL PROTECTED]> wrote: > > I know that. Changes in chrome/VERSION do not reflect in the compiled > chrome.dll, at least on my machine. Also, the svn version number shown > in "about:version" is also frozen unless I do a full rebuild. > > On Sep 26, 2:28 am, Darin Fisher <[EMAIL PROTECTED]> wrote: > > The version number is specified in the chrome/VERSION file. The build > > system should automatically detect changes to that file. We don't change > > that file too frequently.... > > -Darin > > > > On Thu, Sep 25, 2008 at 10:47 PM, Wei Hu <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > > It seems that the version number is updated the first time I do a full > > > build. Afterwards, if I svn up the source code files and do > > > incremental builds, the version number of chrome.dll is frozen. This > > > is problematic because if I ask Chrome about its version number, I get > > > out-dated information. What's the minimal work to ensure the version > > > number of chrome.dll gets updated? > > > > > Thanks, > > > Wei > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
