[PyQt] ANN: pyqtdeploy v2.0 Released

[Patrick Stinson]

So is your suggestion is to patch pyqtdeploy for each application to include the source files and module unit entry, or is there a cleaner way to do it?

> On Jan 6, 2018, at 2:34 AM, Phil Thompson <phil at riverbankcomputing.com> wrote:
> 
>> On 6 Jan 2018, at 5:39 am, 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.
> 
> No. Those modules are built on an application by application basis when needed.
> 
> Phil