On 05/11/2016 02:42 AM, Ms2ger wrote:
On 11/05/16 08:36, Jim Blandy wrote:
It looks like the lack of any CI of the SM-only distribution is a
non-trivial source of pain. That seems independent of where the Rust JSAPI
bindings live, and indeed, independent of Rust altogether.
The SpiderMonkey engineers build the library separately from the rest of
Firefox all the time; the "JS shell" is the preferred development vehicle.
So we can trust that the stand-alone SM builds work. That means that the
difficulties are specific to the process of producing an SM-only tarball.
I've been meaning to add a CI job for generating the tarball and release
libraries, and linking something against it. I can do it for linux64 and
linux32 without much difficulty. It has been a lower priority since I
didn't think many people would be using it; it was just a way to reduce
the burden of fixing up things before every SM release. But given that
it's relevant for Rust, I can bump it up.
OSX and Windows would be harder, just because of the state of
Taskcluster support for those platforms. I have the vague impression
that those are coming along, so I'd rather wait for them rather than
diving down an uncertain rabbit hole.
Note that Servo (and SpiderNode) use --disable-shared-js, which I don't
think is the configuration the shell uses, and which seems to be broken
right now.
Oh. Yeah, that is a little freaky. Bug 1176787 is related, and I was
kind of waiting for it to be resolved before declaring an official SM45
release.
I think it would be generally useful to reduce the number of
configurations that we support, and make sure all supported
configurations run in automation.
Agreed.
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
