<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I will also add that sip5 finally allowed me to get my pyqt5 project with in-app C++ extensions running on Windows in dev where I never really got it running with sip4.<div class=""><br class=""></div><div class="">Though I am still trudging through windows.h compiler errors in my release sysroot built from pyqtdeploy-sysroot and referenced from pyqtdeploy-build, I never got this far before sip5.</div><div class=""><br class=""></div><div class="">I think that is a big deal.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 9, 2020, at 12:07 PM, Patrick Stinson <<a href="mailto:patrickkidd@gmail.com" class="">patrickkidd@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Looping back here after having time to verify how all this works.<div class=""><br class=""></div><div class="">sip5 becoming a self-contained build system finally made it possible to develop a pyqt5 app continuing proprietary sip extensions using the <a href="http://qt.io/" class="">qt.io</a> and <a href="http://python.org/" class="">python.org</a> installers.</div><div class=""><br class=""></div><div class="">Though I see conceptual inconsistencies between how in-app sip extensions are handled by sip-build in the dev phase and pyqtdeploy-sysroot/pyqtdeploy-build in release phase, I think that overall the ability to use a python virtual env in dev instead of building everything from source removes a major bottleneck for pyqt5 developers.</div><div class=""><br class=""></div><div class="">I just hope the concepts don’t all change again with sip6….<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Sep 2, 2020, at 9:52 AM, Patrick Stinson <<a href="mailto:patrickkidd@gmail.com" class="">patrickkidd@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">That is correct. Phil did say that earlier. I appreciate both of your patience as I soak this info up.<div class=""><br class=""></div><div class="">I will move additional questions to new threads.</div><div class=""><br class=""></div><div class="">-Patrick<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Sep 2, 2020, at 3:04 AM, michael h <<a href="mailto:michaelkenth@gmail.com" class="">michaelkenth@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 1, 2020 at 8:18 PM Patrick Stinson <<a href="mailto:patrickkidd@gmail.com" target="_blank" class="">patrickkidd@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Indeed. I have been putting off understanding sip5 but I just went through it all. It took a while to understand from the docs, but nice work.<br class="">
<br class="">
It looks like the correct way to get the .sip files installed for PyQt5 is to use sip-install or PyQt-Builder to install PyQt5 from source?<br class=""><br class=""></blockquote><div class="">Not sure if I missed something in the thread about building from source, but if you install PyQt5 from the wheels on pypi it will include the sip files...in PyQt5/bindings iirc...</div></div></div>
</div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>