Re: [Development] Qt5*Config.cmake files: _qt5_*_check_file_exists macros and plugins

2014-10-20 Thread Rex Dieter
Lisandro Damián Nicanor Pérez Meyer wrote: > On Friday 17 October 2014 17:02:04 Kevin Kofler wrote: >> Hi, > > tl;dr; We have found the same problem in Debian, but steveire told us that > the idea of those CMake files is to provide a way to find the plugins if a > developer is doing it's own inst

Re: [Development] Qt5*Config.cmake files: _qt5_*_check_file_exists macros and plugins

2014-10-19 Thread Stephen Kelly
Kevin Kofler wrote: > > Those _qt5_*_check_file_exists checks look unnecessary to me in the first > place. Part of the intention of the way CMake config-packages and IMPORTED targets work is that if the FooConfig.cmake is present and found, and the Foo IMPORTED target is present, then you can

Re: [Development] Qt5*Config.cmake files: _qt5_*_check_file_exists macros and plugins

2014-10-17 Thread Lisandro Damián Nicanor Pérez Meyer
On Friday 17 October 2014 17:02:04 Kevin Kofler wrote: > Hi, tl;dr; We have found the same problem in Debian, but steveire told us that the idea of those CMake files is to provide a way to find the plugins if a developer is doing it's own installer. So far our solution has been to not ship *Plu