Thanks for your thoughts!
Yes, I was reading about this, which is what prompted me to search and confirm that it was the case. My approach was:
$ rg \
--no-filename \
--no-line-number \
--multiline-dotall '.*\b((native)?[bB]uildInputs) = \[.* cmake.*\];' \
--replace '$1' |
sort |
uniq -c
1 buildInputs
1551 nativeBuildInputs
I’m running this on a release-23.05
checkout; the 1 exception above was fixed here: xplorer: move cmake to nativeBuildInputs · NixOS/nixpkgs@c8929e4 · GitHub
Interesting – I still haven’t figured out this issue, but I’ve never done C or C++ development, so I’m not surprised it’s taking me a while.
I have it building: nix-cadquery/flake.nix at 3adc4c1590b46a00b57d8826548184c7789199c8 · n8henrie/nix-cadquery · GitHub – as mentioned, these were just examples of the types of questions I was hoping to answer by searching nixpkgs.
So it sounds like your general approach is “grep nixpkgs and manually review / refine results.” Is that a fair characterization?