[PyQt] ANN: pyqtdeploy v2.0 Released

[Patrick Stinson]

Also, I have my own qt edits in a single repo and then do a remote build by calling qt’s configure from whatever empty build dir I chose, either passing “developer-build” or “prefix” to install in place in the build dir. Here is my configure line:

../../../pyqt-sysroot-base/src/qt5/qtbase/configure -static -debug-and-release -xplatform macx-ios-clang -nomake examples -nomake tests -opensource -confirm-license -qt-pcre -developer-build

This makes for an easy distclean because you just delete the build dir. Is there a way to do this with pyqtdeploy-sysroot? It doesn’t look like the “source” or “qt_dir” don’t quite accomplish this.

Thanks!



> On Jan 5, 2018, at 9:39 PM, Patrick Stinson <patrickkidd at gmail.com> wrote:
> 
> Phil,
> 
> I had patched pyqtdeploy-v1 to include some standard C python modules in my sysroot builds, for example:
> 
>         {"time", PyInit_time},
>         {"math", PyInit_math},
>         {"pickle", PyInit__pickle},
>         {"_datetime", PyInit__datetime},
>         {"_struct", PyInit__struct},
>         { "binascii", PyInit_binascii},
>         { "_sha512", PyInit__sha512},
>         { "_sha256", PyInit__sha256},
>         { "_sha1", PyInit__sha1},
>         { "_md5", PyInit__md5},
>         { "_random", PyInit__random},
>         { "_zlib", PyInit_zlib},
>         { "_socket", PyInit__socket},
>         { "select", PyInit_select},
> 
> I suppose it makes sense that I am running into some unresolved symbols (_ffi_call_unix64, _ffi_closure_unix64) using this sysroot with the new pyqtdeploy-build. So I guess I should re-build my sysroots using the new pyqtdeploy-sysroot.
> 
> Is there a way to include std c python modules when building python with pyqtdeply-sysroot? In pyqtdeploycli v1 that involved changes to config_py3.c & python.pro.
> 
> Thanks!
> 
>> On Jan 5, 2018, at 6:05 AM, Patrick Stinson <patrickkidd at gmail.com <mailto:patrickkidd at gmail.com>> wrote:
>> 
>> Excellent Phil, nice work. I will definitely get back to you with any feedback.
>> 
>>> On Jan 5, 2018, at 3:30 AM, Phil Thompson <phil at riverbankcomputing.com <mailto:phil at riverbankcomputing.com>> wrote:
>>> 
>>> pyqtdeploy v2.0 has been released. While changes to the GUI are minimal, it should now be much easier to create target-specific system root directories that contain all the components that make up an application.
>>> 
>>> All current versions of Python are now supported.
>>> 
>>> Phil
>>> _______________________________________________
>>> PyQt mailing list    PyQt at riverbankcomputing.com <mailto:PyQt at riverbankcomputing.com>
>>> https://www.riverbankcomputing.com/mailman/listinfo/pyqt <https://www.riverbankcomputing.com/mailman/listinfo/pyqt>
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20180105/12816bcf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1403 bytes
Desc: not available
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20180105/12816bcf/attachment.bin>