-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
'ninja -t compdb' should dump every rule #1377
Comments
I'm also confused by this tool. I don't have problems passing rule names like cc cxx if they exist, but my problem with it was that I figured with no arguments, it should dump every rule it knows about, and only fallback to filtering when you give it arguments to do so. I'm not sure if it's the project I work on or CMake, but when run using CMake in this project, the rule names are incredibly baroque and plentiful, so typing them all out is a non-starter for me. Instead, I use this patch to the package on my Ubuntu computer,
I never bothered cleaning it and posting to the list, because CMake provides it's own way to generate compile commands, but the above might help you in your situation. |
That sounds reasonable to me. |
As mentioned on #1024 (comment) , I think this would be a good change. |
yes please..... |
I'm trying to use the compdb generation functionality of ninja, but it seems to just output
[\n]
every time. There's no documentation for this option, so it seems like there should be no other requirements than to run the command with a valid -C option?Using ninja version 1.8.2 in case that matters.
The text was updated successfully, but these errors were encountered: