D5632: Look for Cppcheck & heaptrack as RUNTIME dependencies
Friedrich W. H. Kossebau
noreply at phabricator.kde.org
Fri Apr 28 12:33:03 UTC 2017
kossebau added a comment.
In https://phabricator.kde.org/D5632#105488, @kfunk wrote:
> Uh, careful here. This suggests those binaries are *required* at runtime.
>
> From https://cmake.org/cmake/help/v3.0/module/FeatureSummary.html:
>
> > Last, a RUNTIME package is a package which is actually not used at all during the build, but which is required for actually running the resulting binaries.
>
> Please make double-sure packagers are aware this is only a *suggestion*, not required at runtime for KDevelop to function properly. Maybe rephrase the `PURPOSE` field:
> `PURPOSE "Suggestion: Required for the heaptrack plugin"`?
Okay, will do a fix-up commit.
> TBH, I'm not sure we need this patch at all.
One thing that needs improvement currently is that the heaptrack and cppcheck plugins are active by default, and inject their actions into the UI enabled even if there is no cppcheck or heaptrack installed at all. Which was my starting motivation for this patch.
Still if optional I think noting the optional runtime deps in cmake summary result is a good way to make packagers and other people building it aware of these dependencies.
CMake should rather be improved to make RUNTIME something orthogonal to OPTIONAL/RECOMMENDED/REQUIRED.
REPOSITORY
R32 KDevelop
REVISION DETAIL
https://phabricator.kde.org/D5632
To: kossebau, #kdevelop, apol, kfunk
Cc: kfunk, kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170428/97394b16/attachment.html>
More information about the KDevelop-devel
mailing list