ktorrent proper doesn't depend on avahi, but it has an optional plugin that does, and by default the build system checks to see if avahi is present. There's an old Gentoo patch that I think is intended to provide support for explicitly disabling avahi (thus killing the check and just not building the plugin) via a configuration option, but it obviously won't apply if ktorrent has been converted to CMake.
In other words, the warning is harmless if you're okay with autodetects, but we may be able to fix it anyway.
Any chance you could find the patch? I should be able to massage into our tqt3/renaming framework.
I realize there is no harm, but I like clean builds and a tad of "spit polish." :-)
Darrell
On Tue, 13 Aug 2013 18:02:36 -0500 "Darrell Anderson" darrella@hushmail.com wrote:
ktorrent proper doesn't depend on avahi, but it has an optional plugin that does, and by default the build system checks to see if avahi is present. There's an old Gentoo patch that I think is intended to provide support for explicitly disabling avahi (thus killing the check and just not building the plugin) via a configuration option, but it obviously won't apply if ktorrent has been converted to CMake.
In other words, the warning is harmless if you're okay with autodetects, but we may be able to fix it anyway.
Any chance you could find the patch? I should be able to massage into our tqt3/renaming framework.
I've attached it. If I'm reading it correctly, once it's applied, you pass --without-avahi to disable the relevant code.
Note that I don't actually use ktorrent—I'm mostly just reading old ebuilds.
I realize there is no harm, but I like clean builds and a tad of "spit polish." :-)
Nothing wrong with a little polish.
E. Liddell
-
Darrell Anderson -
E. Liddell