Discussion: CMake based native module build system proposal

[unbornchikken]

You guys did kinda revolution here in this fork. Don't you think by riding the winds of change is it the time to replace node-gyp with another build system?

I propose CMake. It's mature, fast, stable, has a friendly license, used natively by almost all cross platform C++ IDE-s, and of course, there already exists a node-gyp like module to integrate it with the npm ecosystem (the author is me). It has nice features, like it uses Ninja and Clang if present. Created module has no dependency on Python 2.x, only CMake.

I created a tutorial if you interested, and because it's based on (almost standard) CMake, I can develop and debug my native modules even in stuff like Qt Creator.

I'm here because of two reasons:

• I need a high reach. Without anyone notice that there are other options available than node-gyp for creating native modules, there aren't really other options available.
• I want to know the opinion of this community. If you all think that this idea is just plain stupid, node-gyp is and will be the Holy Way of building native modules for now and forever, then I won't put more effort into it.

[Fishrock123]

There is already a good amount of older discussion about what to do with gyp in #133

[unbornchikken]

Yea, I've already been throug that. I'm here because I created a replacement, not to discuss about what should be created i n the future. Maybe it is not the right solution, but it works, and have its benefits for sure.

[jbergstroem]

@unbornchikken unless there's a PR I think the discussion of which build system to build or adapt better belongs in #133. I'm happy to discuss CMake, but let's not create another thread -- it'll only make backtracking and following discussions harder.

[unbornchikken]

Ok, I understand. I'll put my proposal there later.