I'm guessing you didn't follow the documentation here: http://dev.chromium.org/developers/how-tos/get-the-code
In short, you should use gclient (or bootstrap with the tarball and then update with gclient). gclient is what we use to manage dependencies, such as v8. Just doing an "svn update" is not a good idea as that doesn't have any notion of the dependencies. Using "gclient sync" makes sure that Chromium, and all of its dependencies, are at the proper version. -Ian On Wed, Jan 21, 2009 at 8:23 PM, noemata <[email protected]> wrote: > > I realise building Chromium with VS2008 is unsupported, but it seems > like some progress has been made in this direction with more recent > changes. I was surprised to discover that merely following the build > docs as prescribed does not deliver a fully working setup unless you > are prepared to poke around for sources to a non-trivial degree. > > Here was my experience, which may help others. > > I used Tortoise svn to grab the latest snapshot. That went throgh > without issue, but the list of items below was missing from the build > tree: > > googleeurl - got it from here (http://google-url.googlecode.com/svn/ > trunk/ <http://google-url.googlecode.com/svn/trunk/>) and placed under src > v8 - got it from here (http://v8.googlecode.com/svn/trunk/) and placed > under src > icu38 - moved from deps\third_party into src > gtest - got it from here (http://googletest.googlecode.com/svn/trunk/) > and placed under src\testing\gtest > > Unless I made a mistake somehow, there is no way anyone can get a > working build environment for VS2005 without rummaging around as I > did. > > With these items in place I got a fairly clean conversion of all > VS2005 solution and project files. > > Then I ended up mucking with environment variables to get some of the > build tools work. I've only had partial success with this as some of > the batch files are failing. There are non-Cygwin alternatives too > all the tools being used, by the way. > > I'm surprised by all of the various tools being used for similar > purposes. Given that Python or Perl can do all sorts of heavy > lifting, why is bash in the mix? Why are batch files being used? > This may be needlessly complicated and convoluted. > > So ... I have 95% of things building using VS2008. There do not > appear to be any specific issues with using VS2008 other than figuring > out what's missing, what goes where, and what needs to be tweaked to > get around the somewhat convoluted usage if different tools. > > At a minimum, I think it's time to have VS2008 project files in the > standard source distribution, even if the build process breaks. Or > make sure the VS2005 projects will convert without issue. > > Has anyone gotten all the way there with VS2008? I'd be interested in > collaborating with someone that is wading through the process. > > I must say the sources are Cool, lots of invaluable insights. Now if > only code could be leveraged more easily. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
