5 commits

Author	SHA1	Message	Date
Charles Lowell	8d1e348de0	Try to load the (maybe) active libv8 gem on build ... Sometimes your rubygems install can get into a state where the gem activation succeeds, but the require will ultimately fail. Make sure that the gem is actually available before trying to build with it.	2012-06-25 12:24:30 -05:00
Charles Lowell	a318291c5a	require rubygems before activating libv8	2012-06-20 07:24:08 -05:00
Charles Lowell	478d99b72f	move object access to the class layer.	2012-06-15 09:57:42 -05:00
Charles Lowell	761856b050	link against the shared object by default.	2012-06-14 11:47:00 -05:00
Charles Lowell	fc4d0ce3bf	remove the dependency on libv8	2012-06-14 07:26:33 -05:00