Identifying unnecessary #includes
unnamedrambler at gmail.com
Sat Mar 27 19:06:50 UTC 2010
Hey KDev Devs,
Amarok is working on re-organizing our code base, such that is is
compartmentalized into libraries with few inter library dependencies.
Over the years our source files have gathered many #includes that are
cruft. Aside from manually going through hundreds of files and testing
via trial and error, we are looking for a way to identify and remove
We figured KDev4 and its DU chains might be able to help us. Could
someone comment on this please?
More information about the KDevelop-devel