--
You received this message because you are subscribed to the Google Groups "ninja-build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja-build...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/1033bedc-2102-4af5-b539-7c5829e868b2%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/CACfYaaW2zh9b7JMFr6iPVZbYZwv4wSwacbONBzmzO8saiTmyRg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/CAFOH3pRD%2BrBGv9ZN_6VJy0QQ2rCU6x%3Di5w_nyFVOEO6hhqNA1Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/CAEoffTDioz-Xjp4xrzjH%2Bug_WUk3VKY%2Bj%2BavKbyph4RMrN2W7A%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/1033bedc-2102-4af5-b539-7c5829e868b2%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ninja-build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/CACfYaaW2zh9b7JMFr6iPVZbYZwv4wSwacbONBzmzO8saiTmyRg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "ninja-build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/CAFOH3pRD%2BrBGv9ZN_6VJy0QQ2rCU6x%3Di5w_nyFVOEO6hhqNA1Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "ninja-build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja...@googlegroups.com.
In the limit, Ninja doesn't know all the files a given command uses -- e.g. the C compiler/linker will search all over your disk looking for header files and libraries. At the other extreme, I suspect your build system knows more than Ninja about which files a given command uses. Those facts together suggest to me that Ninja might not be the right layer for this feature, but I haven't thought about it too hard.
On Thu, Jan 9, 2020 at 7:18 AM Charles Nicholson <nicho...@verily.com> wrote:
We have an appetite for this functionality as well, though it wasn't immediately obvious to us if it should be a ninja or GN feature (I don't think we have a strong preference either way, so pushing it lower seems more generally useful). It's very helpful for medical device regulations and compliance to have automation answer the question of "which modules are covered by which tests?". Of course that alone doesn't answer the question but it's a very helpful starting point, and good supporting evidence.Charles
On Thu, Jan 9, 2020 at 7:34 AM 'Nicolas Arciniega' via ninja-build <ninja...@googlegroups.com> wrote:
Hello,--I'm working on a Chromium change that would benefit from being able to list out all inputs for a given target. I've included full details for the change if that's interesting.Today, there exists the "commands" tool that spits out all commands required to build a given target(s). I'd like to do basically the same thing, but only printing out inputs. I've got this working locally and I think it'll be a fairly simple change. Would this be a tool that would be interesting to others? I'm happy to put together a pull request for it.More context on the Chromium Change:I'm working on an update to the Auditor tool for Network Traffic Annotation. In short, these annotations are meant to clearly describe the intent of each network call going through the Chromium network stack. The auditor tool ensures each annotation is correctly formatted and documents existing annotations. Today, the auditor tool does not audit test files. We'd like to be able to audit test files and, more generally, all files that don't ship in the product so that we can we can ensure that these only use the "TEST" annotation. This will help make sure that the documentation compiled for annotations is completely accurate.In order to accomplish this, we need to figure out a way to identify which files don't ship with the product. One way of achieving this would be to create a ninja tool that tells us each input in the "shipped_binaries" target. Each source file that is not in the output of this new ninja tool would be identified as a file that does not ship in the product.Thanks,Nicolas
You received this message because you are subscribed to the Google Groups "ninja-build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ninja-build/1033bedc-2102-4af5-b539-7c5829e868b2%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ninja-build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ninja...@googlegroups.com.