Well, I use them when building and debugging V8 on Windows, which is not as frequent as it used to be.
I think there should be a simple way to work work with V8 in Visual Studio, and making a set of project files that will work is not a simple task, so I vote for keeping them. There is also a version issue here, as the file format for Visual Studio 2008 is not the same as for Visual Studio 2005. The current files can be converted to Visual Studio 2008 with some warnings. One other solution would be to use the gyp files used by Chromium to generate Visual Studio project files - I don't know how much work that would take. Regarding the x64 Windows build it is not something that we check up on on a regular basis. I had to fix the build today due to warnings, so here it is not only the Visual Studio files which suffer. I will volunteer to run through these files to make sure they work and convert to Visual Studio 2008 without warnings if possible. /Søren On Tue, Jan 26, 2010 at 17:01, Kevin Millikin <[email protected]>wrote: > We have some Visual Studio build files in tools/visual_studio. > > Does anyone care about these? It looks like the x64 ones won't work at all > right now, and possibly not the arm simulator ones either. > > I've been making an effort to keep them up-to-date (without testing them) > when I change (add, remove, rename) files. > > Or are they like the xcode project files, and they only need to change when > (a) somebody notices they don't work and (b) cares? > > What say we? > > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
