Strange commit to FindKDE4Internal.cmake
steveire at gmail.com
Sun Feb 19 22:12:20 UTC 2012
Pau Garcia i Quiles wrote:
> On Sun, Feb 19, 2012 at 5:20 PM, Alexander Neundorf <neundorf at kde.org>
> Now try and find a LibFooConfig.cmake somehow. Absolutely impossible.
> Heck, many times headers and libraries will be under some shared
> network drive! (something like H:\lib + H:\include). Are you going to
> scan every drive connected to the computer looking for config files?
How would FindFoo.cmake know where to look?
> - Libraries (libfoo) must always provide a reference FindLibFoo.cmake
> in the package and make it available for third party developers in the
> tarballs. Packages (libfoo-dev) must install this
Brad on the CMake list suggested that such files would belong in the
documentation of libfoo (libfoo-doc package), which I thought was an
interesting point (Or in any other documentation it could be a snippet).
If installed with the -dev package (even as a reference implementation or a
template), it's kind of back to the situation of putting the treasure map
with the treasure. However, if it's part of documentation, presumably the
person using it will read that documentation and see it.
More information about the Kde-buildsystem