Re: Relevance of generated .c and .cpp files in the obj-* directory for mozilla's code dependencies

2014-02-28 Thread Gregory Szorc
On 2/28/2014 7:12 AM, konstantin.sokolov.m...@gmail.com wrote: > Am Freitag, 28. Februar 2014 14:45:18 UTC+1 schrieb Boris Zbarsky: >> Whether you want to include them probably depends on what you're measuring. > > One of the aims is to "measure" the evolution of dependencies within the code > ba

Re: Relevance of generated .c and .cpp files in the obj-* directory for mozilla's code dependencies

2014-02-28 Thread konstantin . sokolov . mail
Am Freitag, 28. Februar 2014 14:45:18 UTC+1 schrieb Boris Zbarsky: > Whether you want to include them probably depends on what you're measuring. One of the aims is to "measure" the evolution of dependencies within the code base over time, in order to identify problematic trends (let's say ones,

Re: Relevance of generated .c and .cpp files in the obj-* directory for mozilla's code dependencies

2014-02-28 Thread Boris Zbarsky
On 2/28/14 7:46 AM, konstantin.sokolov.m...@gmail.com wrote: We wonder what the relationship is between the initial code base and these generated files. It depends. Some of these are autogenerated (from IDL) glue code for calling between JS and C++. Some are autogenerated (from IPDL) glue

Relevance of generated .c and .cpp files in the obj-* directory for mozilla's code dependencies

2014-02-28 Thread konstantin . sokolov . mail
Hi All! We would like to analyze mozilla's code base in order to visualize dependencies and other code metrics. After the build a lot of *.c and *.cpp files have been created under /obj-x86_64-unknown-linux-gnu. We wonder what the relationship is between the initial code base and these generate