-
-
Notifications
You must be signed in to change notification settings - Fork 16.7k
cc-wrapper: generating compile_commands.json using cc-wrapper #192694
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
Conversation
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
6fc914a
to
4ef9345
Compare
still tinkering a little with the mini compile commands code. Should have it settled by later today |
891f054
to
de22708
Compare
c569071
to
2306333
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review/3032/1238 |
47bd5c5
to
ae0886c
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
ae0886c
to
ee89e01
Compare
After at first being confused what this is supposed to be about and then reading the linked Discourse thread, this seems like a valuable addition. Once someone approves technical fitness, please ping me for a review of the user-facing documentation. I can't promise to take a lot of time or be very quick, but I really would like this to be at least reasonably good and fear that otherwise it will be quite useless to the uninitiated. Sorry if this sounds harsh - I really appreciate your contribution! But I can't even quickly make constructive comments without a few basic preconditions:
Usually I'd jump in as a test subject, but there's only so much I can do in a day, and this topic is too far away from my current priorities. And yet, I would veto merging this PR before documentation is in a state that is worthwhile to discuss in more detail. |
Thanks for the feedback @fricklerhandwerk! very much appreciated. Will get to work on addressing the issues. |
…i-compile-commands
36dadb4
to
0b9c3e2
Compare
OK, I have put each sentence in the docs on a new line, which hopefully will make discussing easier. I totally agree that currently, I am not doing a fantastic job explaining. I think the main issue is that there are two orthogonal things happening here, and I am conflating them.
I 100% agree that nix documentation is one of its weak spots, and am committed to getting the documentation right in this case! I'll start accumulating commits until we have this resolved so that we don't lose comments. Will squish down at the end. |
This will make CLion integration with Nix first class right? |
@fzakaria: I haven't used CLion before, but based on my reading of https://www.jetbrains.com/help/clion/compilation-database.html, I would say yes |
I was just digging around in the
which is exactly what I am adding to the Does anyone know why the compilers are |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
d751537
to
b21d11d
Compare
Description of changes
Modifying the cc-wrapper so that it can be used to generate
compile_commands.json
files. Here is the corresponding package:https://github.com/danielbarter/mini_compile_commands
Inserts a
post-wrapper-hook
which the user can provide to insert a hook into the wrapper.mini-compile-commands
provides the functionmini-compile-commands.wrap
which can be used to add compile command generating functionality to a standard environment:Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes