Re:https://testresults.qt.io/coin/api/log/qt/qtbase/ 3cd67f71eccb54c0725e2f041d52df0f38c8db73/ LinuxUbuntu_22_04x86_64QNXQNX_710x86_64GCCqtci-linux-Ubuntu-22.04-x86_64-51- add35eUseConfigure/8747173571fbffbc9616350fba1566cc606a3003/build_1700090991/ log.txt.gz
CMake said:
-- Performing Test HAVE_sysv_shm
-- Performing Test HAVE_sysv_shm - Failed
-- Performing Test HAVE_sysv_sem
-- Performing Test HAVE_sysv_sem - Failed
-- Performing Test HAVE_posix_shm
-- Performing Test HAVE_posix_shm - Success
-- Performing Test HAVE_posix_sem
-- Performing Test HAVE_posix_sem - Success
...
Defaulting legacy IPC to POSIX ......... no
The condition for the latter is:
qt_feature("ipc_posix"
LABEL "Defaulting legacy IPC to POSIX"
CONDITION TEST_posix_shm AND TEST_posix_sem AND (
FEATURE_ipc_posix OR (APPLE AND QT_FEATURE_appstore_compliant)
OR NOT (TEST_sysv_shm AND TEST_sysv_sem)
)
)
If TEST_posix_shm = TRUE and TEST_posix_sem = TRUE and TEST_sysv_shm = FALSE
and TEST_sysv_sem = FALSE, why is ipc_posix not TRUE?
The only thing I can think of is that CMake said "HAVE" and the conditions are
"TEST".
For obvious reasons I can't debug this.
Would be also nice if someone could confirm whether QT_IPC_POSIX was defined in
6.5 for QNX. I expect it was, and the way this is now it's changing
compatibility.
If it was not defined, then we have bigger problems.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
