v8/tools/visual_studio
kasperl@chromium.org b5a72a1645 Generalized the EvalCache into a CompilationCache and enabled
it for scripts too. In the context of Chromium, this should 
have a very positive impact on memory consumption for web apps
that run multiple tabs from the same domain with a lot of the
same JavaScript code.

For now, the cache retirement policy is really simple:
Whenever a mark-sweep collection is started we clear the
cache. This guarantees that this change will not have a
huge negative impact on memory consumption, but it may
not be ideal. We should consider a more sophisticated LRU
scheme.
Review URL: http://codereview.chromium.org/1933

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@270 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
2008-09-11 10:51:52 +00:00
..
common.vsprops Included mjsunit JavaScript test suite and C++ unit tests. 2008-08-22 13:33:59 +00:00
debug.vsprops Improved performance of garbage collection by changing the way we use the marking stack in the event of stack overflow during full garbage collection and by changing the way we mark roots. 2008-08-13 09:32:07 +00:00
js2c.cmd Improved performance of garbage collection by changing the way we use the marking stack in the event of stack overflow during full garbage collection and by changing the way we mark roots. 2008-08-13 09:32:07 +00:00
README.txt Add Visual Studio solution and Visual Studio project for building the 2008-08-29 09:32:03 +00:00
release.vsprops Improved performance of garbage collection by changing the way we use the marking stack in the event of stack overflow during full garbage collection and by changing the way we mark roots. 2008-08-13 09:32:07 +00:00
v8_base.vcproj Generalized the EvalCache into a CompilationCache and enabled 2008-09-11 10:51:52 +00:00
v8_cctest.vcproj Add Visual Studio solution and Visual Studio project for building the 2008-08-29 09:32:03 +00:00
v8_mksnapshot.vcproj Included mjsunit JavaScript test suite and C++ unit tests. 2008-08-22 13:33:59 +00:00
v8_process_sample.vcproj Included mjsunit JavaScript test suite and C++ unit tests. 2008-08-22 13:33:59 +00:00
v8_shell_sample.vcproj Included mjsunit JavaScript test suite and C++ unit tests. 2008-08-22 13:33:59 +00:00
v8_snapshot.vcproj Included mjsunit JavaScript test suite and C++ unit tests. 2008-08-22 13:33:59 +00:00
v8.sln Add Visual Studio solution and Visual Studio project for building the 2008-08-29 09:32:03 +00:00
v8.vcproj Changed the Visual Studio project files to work when V8 is checked out 2008-09-11 08:05:45 +00:00

This directory contains Microsoft Visual Studio project files for including v8
in a Visual Studio/Visual C++ Express solution. All these project files have
been created for use with Microsoft Visual Studio 2005. They can however also
be used in both Visual Studio 2008 and Visual C++ 2008 Express Edition. When
using the project files in the 2008 editions minor upgrades to the files will
be performed by Visual Studio.

v8_base.vcproj
--------------
Base V8 library containing all the V8 code but no JavaScript library code. This
includes third party code for regular expression handling (jscre) and
string/number convertions (dtoa).

v8.vcproj
---------
V8 library containing all the V8 and JavaScript library code embedded as source
which is compiled as V8 is running.

v8_mksnapshot.vcproj
--------------------
Executable v8_mksnapshot.exe for building a heap snapshot from a running V8.

v8_snapshot.vcproj
------------------
V8 library containing all the V8 and JavaScript library code embedded as a heap
snapshot instead of source to be compiled as V8 is running. Using this library
provides significantly faster startup time than v8.vcproj.

The property sheets common.vsprops, debug.vsprops and release.vsprops contains
most of the configuration options and are inhireted by the project files
described above. The location of the output directory used are defined in
common.vsprops.

With regard to Platform SDK version V8 has no specific requriments and builds
with either what is supplied with Visual Studio 2005 or the latest Platform SDK
from Microsoft.

When adding these projects to a solution the following dependencies needs to be
in place:

  v8.vcproj depends on v8_base.vcproj
  v8_mksnapshot.vcproj depends on v8.vcproj
  v8_snapshot.vcproj depends on v8_mksnapshot.vcproj and v8_base.vcproj

A project which uses V8 should then depend on v8_snapshot.vcproj.

If V8 without snapshot if preferred only v8_base.vcproj and v8.vcproj are
required and a project which uses V8 should depend on v8.vcproj.

Two sample project files are available as well. These are v8_shell_sample.vcproj
for building the sample in samples\shell.cc and v8_process_sample.vcproj for
building the sample in samples\process.cc. Add either of these (or both) to a
solution with v8_base, v8, v8_mksnapshot and v8_snapshot set up as described
above and have them depend on v8_snapshot.

Finally a sample Visual Studio solution file for is provided. This solution file
includes the two sample projects together with the V8 projects and with the
dependencies configured as described above.

Python requirements
-------------------
When using the Microsoft Visual Studio project files Python version 2.4 or later
is required. Make sure that python.exe is on the path before running Visual
Studio. The use of Python is in the command script js2c.cmd which is used in the
Custom Build Step for v8natives.js in the v8.vcproj project.