Details
-
Bug
-
Resolution: Unresolved
-
P1: Critical
-
None
-
6.9
Description
We do not have any Windows config that uses -qtnamespace configure parameter.
As a result, the Windows-specific code that incorrectly uses QT_{BEGIN,END}_NAMESPACE might get merged successfully.
We already have QTBUG-128465 reported by RTA, and when I tried to investigate it, I stumbled upon a newly-introduced bug in QtCore.
We need to add one MSVC configuration that uses -qtnamespace TestNamespace, like it's done for macOS and Ubuntu.
Attachments
Issue Links
- is blocked by
-
QTBUG-133517 Windows LLVM: TestNamespace error with qproperty.h
-
- Reported
-
-
QTBUG-132488 TestNamespace error at Active Qt
-
- Closed
-
-
QTBUG-133516 Windows MinGW: TestNamespace errors in qcomobject
-
- Closed
-
- relates to
-
QTQAINFRA-5945 Make one of the Android configurations namespace'd
-
- In Review
-
Gerrit Reviews
For Gerrit Dashboard: QTQAINFRA-6540 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
587088,3 | Enable -qtnamespace builds on Windows 10 MSVC2022 CI config | dev | qt/qt5 | Status: NEW | 0 | 0 |
602616,8 | Windows: Add nightly targets to check namespace functionality | dev | qt/qt5 | Status: NEW | 0 | 0 |