-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compile_commands_json generator ignores output directory #2305
Comments
Any thoughts? Also noticed this was a bit broken |
When you want a pull request to be merged, please give it a positive review. Every checkmark ✔️ that project maintainers see there gives them confidence that the proposed changes have been looked at and have been deemed both useful and safe to merge into the codebase. Lots of 👍 and "what is the ETA?" comments are easier for maintainers to ignore than ✔️✔️✔️✔️✔️ from several different reviewers. Anyone can review a pull request on GitHub. To do so here:
|
* fix: use generator_output as output_dir fix: nodejs/node-gyp#2305 * Update pylib/gyp/generator/compile_commands_json.py Co-authored-by: Christian Clauss <[email protected]> * Update compile_commands_json.py --------- Co-authored-by: Christian Clauss <[email protected]>
v14.15.4, npm 6.14.10
Linux 5.4.0-62-generic #70-Ubuntu SMP Tue Jan 12 12:45:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
Steps to reproduce
Generate
compile_commands.json
:Expected behavior
The command above produces two files
Debug/compile_commands.json
andRelease/compile_commands.json
in thebuild
directory likemake
generator:Actual behavior
The command above produces two files
Debug/compile_commands.json
andRelease/compile_commands.json
in the current directory:Verbose output:
The text was updated successfully, but these errors were encountered: