The functionality will be added (that is, if I don't get bored) one thing at a time with the spec.
If you want to test, point the libv8 gem (in Gemfile) to its trunk branch & my changes at stormbreakerbg/libv8 @ trunk.
What works currently is getting V8 to initialize, say its version and create a new Isolate.
Do not break the build process if rubygems cannot be required.
Instread try to require libv8 without selecting a version with gem
and warn the user about it. This is necessary as ruby 1.8 does not
ship with rubygems by default.
therubyracer now delegates all lookup for its v8
compilation dependencies to the libv8 gem.
if you pass the --with-system-v8 flag to the libv8
gem on install, try to configure therubyracer upon
compile with the following options.
--with-v8-include, --with-v8-lib and --with-v8-dir
Otherwise, it will configure therubyracer to use
the vendored version of v8.
move v8 src to google dir
moving v8 source into main extension
move google upstream source dir into v8 ext dir
include v8 library in generated bundle
prep for 0.4.7
roll the upstream build into the main extension build
Documentation was confusing the gem packager.
simplify build instructions with bundled v8.
Only install scons and build v8 if it has not been built already.
Missing CVS.py from the scons library due to ignore patterns.
Don't need libv8 anymore, only python 2.5 which is required to build it.
