Bug 1192188

Summary: cmake doesn't include a fix for mingw32 builds of Qt4
Product: Red Hat Enterprise Linux 7 Reporter: Jan Kundrát <jkt>
Component: cmakeAssignee: Patsy Griffin <pfrankli>
Status: CLOSED ERRATA QA Contact: Martin Cermak <mcermak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: law, mcermak, mnewsome, ngompa13
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cmake-2.8.12.2-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 00:04:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1297579, 1304775, 1313485    

Description Jan Kundrát 2015-02-12 19:43:06 UTC 
This is how trying to cross-build the mingw32 Qt4 version of Trojita ends up on CentOS 7:

-- Package Qt4 is required because of REQUIRED
CMake Error at /usr/share/cmake/Modules/FindQt4.cmake:1055 (set_property):
  set_property could not find TARGET Qt4::QAxServer.  Perhaps it has not yet
  been created.
Call Stack (most recent call first):
  cmake/TrojitaOption.cmake:119 (find_package)
  CMakeLists.txt:109 (trojita_find_package)


CMake Error at /usr/share/cmake/Modules/FindQt4.cmake:1058 (set_property):
  set_property could not find TARGET Qt4::QAxServer.  Perhaps it has not yet
  been created.
Call Stack (most recent call first):
  cmake/TrojitaOption.cmake:119 (find_package)
  CMakeLists.txt:109 (trojita_find_package)


Upstream fixed this in commit b8af46cb878551cc5a1c9275f46792b282479ebb as per http://www.cmake.org/Bug/view.php?id=14165:

cmake $ git tag --contains b8af46cb878551cc5a1c9275f46792b282479ebb
v2.8.11.1
v2.8.11.2

Could you please include that patch in your cmake fixes?
Comment 8 errata-xmlrpc 2016-11-04 00:04:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2175.html