Hi,
Quoting David Tardon <dtardon@redhat.com>:
Hi,
On Tue, Oct 23, 2012 at 10:05:48AM +0200, Miklos Vajna wrote:
Hi David,
On Tue, Oct 23, 2012 at 07:01:36AM +0200, David Tardon
<dtardon@redhat.com> wrote:
> If a source file really contained only unused functions, it would likely
> have been found (and removed) with the help of callcatcher. Of course,
> that would not help if the source were not compiled at all (and we found
> such files on several occasions in the past)... I wonder if it would be
> possible to construct a (more or less) complete list of used source tree
> files from make dependencies; something that could be scripted and run
> periodically to ensure we are not accumulating unused cruft...
Not so easy, I think -- all OSX/Win-specific files are unused in a Linux
build, for example...
That is why I wrote "possible", not "easy" .-)
Often the not easy problems are the most interesting ;-)
Typical distributed process with three steps here:
* first run it on all our main platforms (android, ios, macosx, mingw,
win32, win64 (yes, we have x64 shell extensions), linux32, linux64)
* combine the results
* compare against source tree
Regards
David
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.