-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/01/2013 10:46 AM, Alexander Neundorf wrote:
> [1] Why not merge that into CMake ? For quicker releases, and even easier
> contributing. Also Bill once said that in hindsight he would have prefered if
> cmake would not ship any find-modules itself at all. So one could imagine
> that
> cmake would come without any find-modules in the future, and all find-modules
> would come from a separate package, e.g. ECM.
> This would make cmake the core tool, and ECM its "standard library"
I agree that a separation of CMake and the find_modules make sense. But. Then
it is time to think of a way to integrate cmake with the separate source of
find_modules. Algorithmically, it would look like
PROJECT(MyApplication)
FIND_MODULES_REPOSITORY("http://ecm.kde.org";)
FIND_PACKAGES(KF5 REQUIRED...)
and so forth. That would be a real breakthrough. It is related to the approach
taken by Maven and others. All it takes is a built-in way for CMake to download
the find_modules into a cache location and update them when needed, or on
request.
This would also make a lot of things a lot easier. For example, nobody would
need to separately install ECM, and updates to our ECM packages can be
delivered globally by commits to that repo.
Cheers,
Mirko.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJzgRIACgkQYSSaITCTnKWZ/QCgtW0mTi2WNgdr7KN8H7yxeF0F
HjoAoLE8qKtuPgaemTY/CuOpVPA3Iq/v
=RXy5
-----END PGP SIGNATURE-----
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
