Coverage plugin and geninfo problem
Andreas Pakulat
apaku at gmx.de
Thu Mar 26 07:45:25 UTC 2009
On 26.03.09 01:52:43, Daniel Calviño Sánchez wrote:
> Hi,
>
> after the change to use /usr/bin/geninfo instead of lcov_geninfo
> (http://websvn.kde.org/?view=rev&revision=935308,
> http://websvn.kde.org/?view=rev&revision=935310 and
> http://websvn.kde.org/?view=rev&revision=935311), Coverage plugin
> doesn't seem to work.
>
> When lcov_geninfo was introduced, Manuel Breugelmans made some little
> changes that, as far as I can tell, mostly affected only the output of
> the filenames. That is, instead of, for example, "Processing
> /home/kde-devel/projects/kdevelop/build/projectmanagers/cmake/cmakeutils.cpp",
> the output will remove the working directory and show instead
> "Processing projectmanagers/cmake/cmakeutils.cpp".
>
> However, an additional option to set the current working directory,
> --wcwd, was added in lcov_geninfo and passed when it was executed
> through KDevelop. That option doesn't exist in geninfo, so it
> complaints when executed through the coverage plugin and no coverage
> report is made.
>
> Removing the option from the geninfo call seems to make the coverage
> plugin work flawlessly. However, I don't know whether setting the
> working directory (in KProcess) would be needed or not. I mean, I
> don't know if the working directory makes any difference when geninfo
> is executed (it was set in lcov_geninfo, but maybe it just affected
> the output). In the test I made it wasn't needed, but maybe there is
> some case where it is.
>
> So, should I remove the option where geninfo is called? Remove the
> option and set the working directory in KProcess? Or does it work
> right now and I am missing something?
Unless someone with more background about geninfo comes up with better
answers I suggest to remove the option, but set the current working dir
with KProcess.
Andreas
--
Try the Moo Shu Pork. It is especially good today.
More information about the KDevelop-devel
mailing list