<div dir="ltr"><div>I came up with this when I was working toward modularizing paraview.<br></div>It takes the file you want to inspect as the sole argument, then does a find in the cwd for all of the headers and groups them together into "modules".<br>
<br><div><br></div></div><div class="gmail_extra"><br clear="all"><div>David E DeMarle<br>Kitware, Inc.<br>R&D Engineer<br>21 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-881-4909</div>
<br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 1:32 AM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com" target="_blank">david.gobbi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there a script that can automatically list what modules a<br>
particular .cxx file depends on?<br>
<div class="HOEnZb"><div class="h5"><br>
On Sat, Mar 2, 2013 at 4:49 PM, Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>> wrote:<br>
> I suspect that many of these were left out during modularization. Perhaps<br>
> because they caused dependencies on other modules.<br>
><br>
><br>
> On Saturday, March 2, 2013, David Gobbi wrote:<br>
>><br>
>> I just sent a list of files to vtk-devel that shows what is<br>
>> newly-disabled in master as compared to release.<br>
>><br>
>> And I've attached another file that includes the full path<br>
>> to each disabled test.<br>
>><br>
>> - David<br>
>><br>
>> On Sat, Mar 2, 2013 at 4:10 PM, Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>><br>
>> wrote:<br>
>> > Can you generate this as a list of files? Then one or more of us has<br>
>> > to go through these and either remove them or make them work again.<br>
>> ><br>
>> > -berk<br>
>> ><br>
>> > On Sat, Mar 2, 2013 at 5:21 PM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>><br>
>> > wrote:<br>
>> >> There are also a number of tests that aren't being run. I wrote a<br>
>> >> python script (attached) that looks through all the Testing<br>
>> >> directories and identifies test programs that don't appear in a<br>
>> >> CMakeLists.txt file. It reports:<br>
>> >><br>
>> >> 166 out of 1770 tests are not enabled<br>
>> >> 44 are commented out, the rest are unlisted in cmake<br>
>> >><br>
>> >> Compare this to VTK 5.10:<br>
>> >><br>
>> >> 54 out of 1213 tests are not enabled<br>
>> >> 21 are commented out, the rest are unlisted in cmake<br>
>> >><br>
>> >> It's probably more informative to list the tests by language:<br>
>> >><br>
>> >> Cxx: 132 not enabled (39 in cmake but commented out)<br>
>> >> Tcl: 19 not enabled (2 in cmake but commented out)<br>
>> >> Python: 15 not enabled (3 in cmake but commented out)<br>
>> >><br>
>> >> Recently Bill and others have done an awesome job of reactivating tcl<br>
>> >> and python tests, but a large number of C++ tests are still<br>
>> >> missing/disabled.<br>
>> >><br>
>> >> - David<br>
>> >><br>
>> >><br>
>> >> On Sat, Mar 2, 2013 at 1:46 PM, Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>><br>
>> >> wrote:<br>
>> >>> Yup. One other thing that we would like to try in the near future is<br>
>> >>> to look at combined VTK + ParaView coverage of VTK. ParaView tests<br>
>> >>> some of VTK more thoroughly and that should increase coverage further.<br>
>> >>> I am hoping for 70%. Beyond that, we will have to write more tests.<br>
>> >>><br>
>> >>> -berk<br>
>> >>><br>
>> >>> On Sat, Mar 2, 2013 at 10:08 AM, Bill Lorensen<br>
>> >>> <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>> wrote:<br>
>> >>>> Berk,<br>
>> >>>><br>
>> >>>> Looks like tcl and python were added to ubuntu coverage. Now it is<br>
>> >>>> showing<br>
>> >>>> 66%.<br>
>> >>>><br>
>> >>>> Bill<br>
><br>
><br>
><br>
> --<br>
> Unpaid intern in BillsBasement at noware dot com<br>
><br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</div></div></blockquote></div><br></div>