ios: PyQt incorrectly including QProcess

Patrick Stinson patrickkidd at gmail.com
Sun Apr 6 18:49:17 BST 2025


Actually, I removed the “disabled features” section in my toml and it fixed it. Must have broken some part of the dependency matrix that makes the PyQt_Process flag work.

> On Apr 6, 2025, at 1:47 AM, Phil Thompson <phil at riverbankcomputing.com> wrote:
> 
> On 06/04/2025 06:29, Patrick Stinson wrote:
>> I am getting this error on PyQt5 building a pyqtdeploy sysroot for iOS:
>> qobject.sip:380:10: error: use of undeclared identifier ‘sipName_QProcess'
>> qobject.sip:380:29: error: use of undeclared identifier ‘sipType_QProcess'
>> Those lines show:
>>    #if !defined(QT_NO_PROCESS)
>>        {sipName_QProcess, &sipType_QProcess, -1, -1},
>>    #else
>> So I guess QT_NO_PROCESS is not getting defined or something since
>> QProcess is not available on iOS.
>> I do still see PyQt_Process in disabled_features in my sysroot.toml
>> which worked some years ago…
>> [PyQt.ios]
>> disabled_features = [
>>    "PyQt_Desktop_OpenGL", "PyQt_MacOSXOnly",
>>    "PyQt_MacCocoaViewContainer", "PyQt_Printer",
>>    "PyQt_PrintDialog", "PyQt_PrintPreviewDialog",
>>    "PyQt_PrintPreviewWidget", "PyQt_Process",
>>    "PyQt_NotBootstrapped"
>> ]
>> installed_modules = [
>>    "QtCore", "QtGui", "QtNetwork", "QtWidgets",
>>    "QtMacExtras", "QtQml", "QtQuick", "QtQuickWidgets"
>> ]
>> Any idea how to fix it? Cheers,
>> -Patrick
> 
> That's usually a sign of remnants from a previous build or a misconfigured build system.
> 
> Phil



More information about the PyQt mailing list