Retiring v8-314

Hey, remember when I said I would keep v8-314 alive? I've changed my mind.


A) It is seriously old. I'm not sure I want to encourage anyone to try to
use it at this point.
B) Upstream v8 looks NOTHING like this package anymore
C) It doesn't build anymore because the giant SConstruct goop it uses is
not compatible with the current SCons. (and it has not built for quite a
while now).
D) I have neither the time nor the motivation to do the work to make it
build again

I think there is some effort to enable v8 headers out of the nodejs bundled
copy, which seems like a much smarter approach, since node is actually
maintaining that v8 codebase.

Alternately, the v8 upstream intends for their code to be a "copylib",
which I find disgusting, but not so much that it outweighs the disgust
level in v8-314.

TLDR: v8-314 is old, deserves to die, so i killed it



Re: Retiring v8-314

By =?utf-8?q?Samue... at 03/15/2019 - 15:19

I've managed to make it build with this simple patch, not sure if everything is correct though in regards to options.

--- SConstruct.old 2012-10-22 15:09:53.000000000 +0200
+++ SConstruct 2019-03-15 19:53:49.595494085 +0100
@@ -1183,7 +1183,7 @@ def AddOptions(options, result):

def GetOptions():
- result = Options()
+ result = Variables()
result.Add('mode', 'compilation mode (debug, release)', 'release')
result.Add('sample', 'build sample (shell, process, lineprocessor)', '')
result.Add('cache', 'directory to use for scons build cache', '')

Re: Retiring v8-314

By =?utf-8?q?Samue... at 03/15/2019 - 13:22

Hi Tom,

What do you suggest to packages that depends on this library, bundle or retire as well?