Stephen Kelly wrote:
Yes, ok I'll take that approach.
This is just a documentation change:
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
Stephen Kelly wrote:
Yes, ok I'll take that approach.
This is just a documentation change:
https://codereview.qt-project.org/#change,26541
Thanks,
Steve
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
Brad King wrote:
On 05/17/2012 09:41 AM, Stephen Kelly wrote:
Great, so choosing the correct imported configuration a solved problem.
I'll point the documentation in of the Qt 5 CMake stuff to that so.
Note that MAP_IMPORTED_CONFIG_CONFIG should not be set by package
configuration files.
Hi there,
In Qt 5 we currently generate IMPORTED_LOCATION_${Config} for the Debug or
Release (or both, depending on platform), depending on how Qt is configured.
If both exist (on windows) and the caller uses CMAKE_BUILD_TYPE == Debug or
Release, the correct location should be used. However,
On 05/16/2012 06:42 AM, Stephen Kelly wrote:
In Qt 5 we currently generate IMPORTED_LOCATION_${Config} for the Debug or
Release (or both, depending on platform), depending on how Qt is configured.
If both exist (on windows) and the caller uses CMAKE_BUILD_TYPE == Debug or
Release, the
