Repository navigation
we need CMakeLists.txt #35118
Description
Activity
We have a strategic initiative to move from gyp to something else, possibly CMake: nodejs/TSC#901. It'll take some time to get it right though
Closing as duplicate.
- addedbuildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.
on Sep 9, 2020 @mmarchini i think that give up gyp and anything about python is good idea. so when to migrate? how many days?
how many days?
We're talking a couple years probably, that's not something that can be done in a single PR or in a single version.
@mmarchini you can talk and talk for many days! but can you first give me CMakeLists.txt? i can not open node source code in jetbrains clion! oh my god. please help me. what IDE do you use?
As mentioned before, adding CMake support is not something we can rush, nor is it an easy task that can be accomplished quickly.
To build Node.js you can follow the instructions on our build guide: https://github.com/nodejs/node/blob/master/BUILDING.md, it contains the appropriate steps and dependencies for each operating system.
what IDE do you use? can you teach me how to open node source code in jetbrains clion?
FWIW, I attempted a port to cmake a few years ago: https://github.com/bnoordhuis/io.js/tree/cmake
The size of the diff says something about the amount of work involved, and ^ supports maybe 50% of the features that the gyp build supports.
I use VSCode + terminal. Just "opening the Node.js source code" should be possible regardless of build system, building it might depend on that's available on Jetbrains. I'm not familiar with Jetbrains specifically so if it has some different requirements I won't be able to help. Working on Node.js with Jetbrains seems to be worth a separate issue though, I suggest opening a new one with as much information as you can provide so other folks can help.
@bnoordhuis can you support 100% features?
@mmarchini libuv source repo have CMakeLists.txt, i believe that node should have one too. we should unify build system. no libuv, no node.If I had infinite time and patience, sure, but I have neither.
Reacted by Denys Otrishko, hinell and hehe
node source code why not have CMakeLists.txt like libuv source code? please give me one.