I think a fundamental thing here is that there's a large world between:
[API changes all the time] -- ... -- [ stable API/ABI ]
In particular, in the middle area, there are small things that the SpiderMonkey consuming community would greatly benefit from that don't restrict SpiderMonkey really. See https://bugzilla.mozilla.org/show_bug.cgi?id=618381 for an example.
Another one is build support code for an independent-of-firefox SpiderMonkey release could be upstream, and it could have an independent version.
So, let me lay out some tasks:
* Land some version of 618318 so that embedders can adapt more easily when API changes
* Move xulrunner/installer/mozilla-js.pc.in into js/src/
* Add a version to the libmozjs.so
* Remove the Firefox configure flag --enable-shared-js
* Add a "make dist" target that generates spidermonkey-X.tar.gz to js/src/Makefile.in
I think a fundamental thing here is that there's a large world between:
[API changes all the time] -- ... -- [ stable API/ABI ]
In particular, in the middle area, there are small things that the SpiderMonkey consuming community would greatly benefit from that don't restrict SpiderMonkey really. See https:/ /bugzilla. mozilla. org/show_ bug.cgi? id=618381 for an example.
Another one is build support code for an independent- of-firefox SpiderMonkey release could be upstream, and it could have an independent version.
So, let me lay out some tasks:
* Land some version of 618318 so that embedders can adapt more easily when API changes installer/ mozilla- js.pc.in into js/src/ X.tar.gz to js/src/Makefile.in
* Move xulrunner/
* Add a version to the libmozjs.so
* Remove the Firefox configure flag --enable-shared-js
* Add a "make dist" target that generates spidermonkey-