The compiler used *may* be another paramater to consider, but I haven't ran into any problems in use with node-bindings yet. One issue getting the compiler name is that it's not available in node anywhere, so getting that value at runtime would be hard/impossible.
On Wed, Feb 1, 2012 at 6:38 PM, Robert Mustacchi <[email protected]> wrote: > On 02/01/2012 04:52 PM, Isaac Schlueter wrote: > >> 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. >> > > There is no stable C++ ABI, so you will also have to add the compiler > version as another argument to that list of targets. Some compilers do try > to do versioning with mapfiles, but it is rarely used. The worst thing that > can happen is having a version of node built with one version of a compiler > and an addon with another. > > Robert >
