On Friday, 28 de October de 2011 13:13:20 Stephen Kelly wrote: > * If you want to be easily found for others to depend on, you write a > <Package>Config.cmake file and install it to a location CMake will use > to find things like that. I assume this is similar to how pkgconfig > works, but I have never used pkgconfig.
Just like pkgconfig, I'd recommend that we make it one file per library, not one global Qt5Config.cmake. Alternatively, let's be very clear: it's Qt5EssentialsConfig.cmake and it includes NO other Qt addon. For those addons, they need to provide the Config files themselves. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development