--===============2812504358303372840==
Content-Type: multipart/signed;
  boundary="nextPart1551149.0kAxoGKDvF";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1551149.0kAxoGKDvF
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Friday 17 of February 2012 17:48:37 Pau Garcia i Quiles wrote:
> On Fri, Feb 17, 2012 at 5:33 PM, Alexander Neundorf <neundorf@kde.org>=20
wrote:
> > A library must never install the Find-module for itself.
> >=20
> > This defeats the purpose. This is like putting the remote control right
> > next to the TV, or the treasure map right into the treasure chest. You
> > don't know where the plan is, but once you found the plan, you already
> > found what you are interested in and don't need the plan anymore.
>=20
> Let me disagree.
>=20
> If I am developing an application which depends on a library, and that
> application may be built on several platforms, I will need a
> FindLibFoo.cmake.
>=20
> If libfoo makes FindLibFoo.cmake available (for instance as part of
> the libfoo-dev package), then I only need to copy it to my "cmake"
> directory.
>=20
> If libfoo does not make FindLibFoo.cmake available, I will need to go
> and look for it somewhere else: Google it? Look for FindLibFoo.cmake
> at some other project's "cmake" directory?
>=20
> It looks like you are recommending the latter. Could you please
> explain why? It does not make sense to me.

=46indXXX.cmake should not be installed to target system because it suggest=
s=20
this file will be somewhat magically available for the client (application=
=20
using FindXXX.cmake).
But it will not and it's it's client's sole responsibility to provide this=
=20
file.

libfoo can of course provide FindXXX.cmake in its source tarball (in=20
misc/sdk/contrib directory for instance) so that libfoo clients may copy it=
 to=20
their buildsystems, but libfoo should never install this file by itself.

=46indXXX.cmake is not .pc file (pkg-config) equivalent as it doesn't provi=
de=20
exact library location in system, just a way to find it.
Like Alex said, it's like a map to find a treasure (exact library location =
in=20
system), and when buried along with a treasure...

=2D-=20
regards
MM

--nextPart1551149.0kAxoGKDvF
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEABECAAYFAk8/6moACgkQFuHa/bHpVdvU1QCgo02h3H7PDFkLD+pGhv37oA5p
qmIAoIx+toDKm0AxtbD0sT+LwDj6o1jj
=w3bB
-----END PGP SIGNATURE-----

--nextPart1551149.0kAxoGKDvF--

--===============2812504358303372840==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem

--===============2812504358303372840==--