Arch Linux

Description:
There appears to be an issue with a changes that made a qt5 cmake macro backwards incompatible.

The issue is pretty well described here as well: https://bugs.gentoo.org/703306

Errors:
CMake Error at /usr/lib64/cmake/Qt5Widgets/Qt5Widgets_QMotifStylePlugin.cmake:4 (_populate_Widgets_plugin_properties):
_populate_Widgets_plugin_properties Macro invoked with incorrect arguments
for macro named: _populate_Widgets_plugin_properties
Call Stack (most recent call first):
/usr/lib64/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:213 (include)
/usr/lib64/cmake/Qt5/Qt5Config.cmake:28 (find_package)
CMakeLists.txt:7 (find_package)

CMake Error at /usr/lib64/cmake/Qt5Widgets/Qt5Widgets_QPlastiqueStylePlugin.cmake:4 (_populate_Widgets_plugin_properties):
_populate_Widgets_plugin_properties Macro invoked with incorrect arguments
for macro named: _populate_Widgets_plugin_properties
Call Stack (most recent call first):
/usr/lib64/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:213 (include)
/usr/lib64/cmake/Qt5/Qt5Config.cmake:28 (find_package)
CMakeLists.txt:7 (find_package)

And so on..

All are related to the macro _populate_Widgets_plugin_properties or more specifically:
macro(_populate_$${CMAKE_MODULE_NAME}_plugin_properties Plugin Configuration PLUGIN_LOCATION IsDebugAndRelease)

Additional info:
* qt5-base 5.14.1-4
* cmake 3.17.0
* config and/or log files etc.
* https://bugs.gentoo.org/703306

Steps to reproduce:
New cmake file

include find_packages for qt5 Widgets & Gui
set(CMAKE_AUTOMOC ON)
set(CMAKE_AUTORCC ON)
set(CMAKE_AUTOUIC ON)
find_package(Qt5 COMPONENTS Gui Widgets REQUIRED)
run cmake

To temporarily fix the issue, I manually edited the macro in /usr/lib64/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake as described below:
-- macro(_populate_Widgets_plugin_properties Plugin Configuration PLUGIN_LOCATION
-- IsDebugAndRelease)
++ macro(_populate_Widgets_plugin_properties Plugin Configuration PLUGIN_LOCATION
++ )
++ set(IsDebugAndRelease FALSE)

I'm not particularly familiar with how the macros are generated, but hopefully this will pinpoint the issue. I've never submitted and Arch bug before, and I'm happy to change or resubmit if I've messed anything up.