On Wed, May 11, 2016 at 8:33 AM, Steve Fink <[email protected]> wrote:
> 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. > Following up on this discussion: I just landed bug 1273917 on inbound, which adds the SM(pkg) task. The SM(pkg) task bundles SpiderMonkey sources up as a tarball release, untars it in another directory, builds the shell, and finally runs jittests/jsapi-tests/js shell tests. _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
