On Wed, Feb 1, 2012 at 16:15, Nathan Rajlich <[email protected]> wrote: > Devs have to now compile for each supported platform and architecture before > publishing
Problem 1 is indeed a problem, but it can be solved in 2 ways. 1. If you have the toolchain installed, you'll be able to build at install time, just like you do today with node-waf, so there's a fallback. 2. We'll build some cloudy buildbot CI stuff to compile all the things. Node-bindings could definitely be handy. > So that leaves problem #1. I like the "addon-gyp-toolchain" module idea. I > hadn't considered that before, and that should help, though I'm not exactly > sure how it would work (currently Windows addons require the node source > tree, so that would need to be fixed I guess). Any addon build would require the node source tree, or at least the headers. Like I said, lots of fiddly little bits to get all in a row, probably some core changes, etc. But, this should happen mostly independent of any changes in node itself. > I'm still envisioning some kind of Travis-CI-like cloud-based build system, > that would receive a git-hook and recompile your module on the various > platforms/archs and commit them back to your repo (or something), whenever a > change happened in the `src` dir. If that was done right, it would make it > painless for both the devs and the uses of the module. Yes, but it should be based on publishes, and attach the tarball to the package in the registry tagged with the appropriate platform indicators.
