On Wed 27 Mar 2013 03:25:20 PM PDT, Bas Schouten wrote: > I would argue this is probably true. As I've talked to a developer from a > large third party where the discussion of if they would try to adjust their > work to Moz2D literally ended at: 'I have to check out -all- of firefox? How > big is that 2 Gig or something?' I think it's certainly the largest practical > and mental barrier.
You only have to require checking out all of Firefox for those who want to modify Moz2D and submit patches back. That's how the JS engine works. It's a regular part of the full mozilla-central tree, but we produce periodic "releases" that are basically tarballs of the js/src subtree. (It's not really nearly that simple, and our releases are very irregularly spaced in time, but let's play pretend for now.) Embedders who just want to use Spidermonkey can download the release tarball, which has its own configure script and everything. The Spidermonkey-only build procedure feels "normal"; you don't have to know about the Mozilla build system or anything. (gps has thankfully preserved this characteristic with recent build changes.) I don't know if this changes the fundamental equation or not. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
