- Version: All
- Platform: Windows
- Subsystem: build
Up till now we have been using two mechanism to build node, on windows vcbuild.bat that triggers configure and then msbuild. And on all other platforms a direct call to configure and then an explicit call to make. Having two mechanisms, leads to divergence, as often bugs-fixes/improvements are done on one and not the other. I wish we could eliminate this disparity by using a tool that works on both platforms.
A few proposed solutions:
- build using
ninja as chromium and V8 does (generate .ninja files with GYP)
- build using
cmake which is now MSVS supported (generate CMakeLists.txt files with GYP)
- investigation build with
make on Windows
Up till now we have been using two mechanism to build
node, on windowsvcbuild.batthat triggersconfigureand thenmsbuild. And on all other platforms a direct call toconfigureand then an explicit call tomake. Having two mechanisms, leads to divergence, as often bugs-fixes/improvements are done on one and not the other. I wish we could eliminate this disparity by using a tool that works on both platforms.A few proposed solutions:
ninjaaschromiumandV8does (generate.ninjafiles withGYP)cmakewhich is now MSVS supported (generateCMakeLists.txtfiles withGYP)makeon Windows