<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">OK, gotcha. So you have to mimic the disabled_features bit there or the build will fail, indicated by this:<div><br></div><div><span style="font-size: 16px; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: sans-serif; background-color: rgb(255, 255, 255);">However how </span><code class="docutils literal notranslate" style="background-color: rgb(236, 240, 243); padding: 0px 1px; font-size: 0.95em; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="pre" style="hyphens: none; white-space: nowrap;">disabled_features</span></code><span style="font-size: 16px; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: sans-serif; background-color: rgb(255, 255, 255);"> is set in the above will be appropriate for most cases.</span></div><div><br></div><div>Thanks for the help,</div><div>-Patrick<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Apr 8, 2025, at 11:51 PM, Phil Thompson <phil@riverbankcomputing.com> wrote:</div><br class="Apple-interchange-newline"><div><div>Check the sysroot.toml file in the demo.<br><br>On 09/04/2025 07:19, Patrick Stinson wrote:<br><blockquote type="cite">Ah ok, so I assume you mean that there isn’t a default set of<br>unsupported features for iOS and you have to disable them explicitly<br>in your sysroot.toml?<br>If so, do you have a list of minimum disabled features for PyQt to<br>build for iOS? So far I’ve run in to PyQt_Process and<br>PyQt_Desktop_OpenGL<br><blockquote type="cite">On Apr 8, 2025, at 12:45 AM, Phil Thompson <phil@riverbankcomputing.com> wrote:<br>On 08/04/2025 05:31, Patrick Stinson wrote:<br><blockquote type="cite">The disabled_features sections of the pyproject.toml that the PyQt<br>plugin writes are empty. That doesn’t seem right, shouldn’t it include<br>PyQt_Process?<br></blockquote>Yes, if they are defined in your sysroot.toml file.<br>Phil<br><blockquote type="cite">[tool.sip.bindings.QtCore]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtGui]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtNetwork]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtWidgets]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtMacExtras]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtQml]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtQuick]<br>static = true<br>disabled-features = []<br>[tool.sip.bindings.QtQuickWidgets]<br>static = true<br>disabled-features = []<br><blockquote type="cite">On Apr 7, 2025, at 9:22 AM, Patrick Stinson <patrickkidd@gmail.com> wrote:<br>Now I’m running into a related problem during the PyQt build:<br>/Users/patrick/dev/lib/Qt/5.15.2/ios/include/QtCore/qglobal.h:294:33: note: expanded from macro 'QT_DEPRECATED_X'<br>294 | # define QT_DEPRECATED_X(text) Q_DECL_DEPRECATED_X(text)<br> | ^<br>/Users/patrick/dev/lib/Qt/5.15.2/ios/include/QtCore/qcompilerdetection.h:675:55: note: expanded from macro 'Q_DECL_DEPRECATED_X'<br>675 | # define Q_DECL_DEPRECATED_X(text) __attribute__ ((__deprecated__(text)))<br> | ^<br>/var/folders/cm/xhqjxbbn6qx1pvft5cw1gdg40000gn/T/tmpgeo7rte2/QtCore/sipQtCorepart0.cpp:73375:30: error: expected class name<br>73375 | class sipQProcess : public ::QProcess<br><blockquote type="cite">On Apr 6, 2025, at 9:49 AM, Patrick Stinson <patrickkidd@gmail.com> wrote:<br>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.<br><blockquote type="cite">On Apr 6, 2025, at 1:47 AM, Phil Thompson <phil@riverbankcomputing.com> wrote:<br>On 06/04/2025 06:29, Patrick Stinson wrote:<br><blockquote type="cite">I am getting this error on PyQt5 building a pyqtdeploy sysroot for iOS:<br>qobject.sip:380:10: error: use of undeclared identifier ‘sipName_QProcess'<br>qobject.sip:380:29: error: use of undeclared identifier ‘sipType_QProcess'<br>Those lines show:<br>#if !defined(QT_NO_PROCESS)<br> {sipName_QProcess, &sipType_QProcess, -1, -1},<br>#else<br>So I guess QT_NO_PROCESS is not getting defined or something since<br>QProcess is not available on iOS.<br>I do still see PyQt_Process in disabled_features in my sysroot.toml<br>which worked some years ago…<br>[PyQt.ios]<br>disabled_features = [<br>"PyQt_Desktop_OpenGL", "PyQt_MacOSXOnly",<br>"PyQt_MacCocoaViewContainer", "PyQt_Printer",<br>"PyQt_PrintDialog", "PyQt_PrintPreviewDialog",<br>"PyQt_PrintPreviewWidget", "PyQt_Process",<br>"PyQt_NotBootstrapped"<br>]<br>installed_modules = [<br>"QtCore", "QtGui", "QtNetwork", "QtWidgets",<br>"QtMacExtras", "QtQml", "QtQuick", "QtQuickWidgets"<br>]<br>Any idea how to fix it? Cheers,<br>-Patrick<br></blockquote>That's usually a sign of remnants from a previous build or a misconfigured build system.<br>Phil<br></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></div></div></blockquote></div><br></div></body></html>