Hey, just wanted to mention that it did work without any issue with the
version 6.5.0.
Thanks for the help!
On Fri, Mar 31, 2023 at 4:32 PM Pedro Ferreira
wrote:
> I'll submit again with that build and see if it works.
> So for v6.5.0 there won't be that *-appstore-compliant *option anymore,
>
I'll submit again with that build and see if it works.
So for v6.5.0 there won't be that *-appstore-compliant *option anymore, it
will be simply already compliant?
Thanks
On Fri, Mar 31, 2023 at 10:28 AM Cristián Maureira-Fredes <
cristian.maureira-fre...@qt.io> wrote:
> Hey Pedro,
>
> Glad you
Hey Pedro,
Glad you managed to reduce the amount of invalid symbols.
There is no other PySide distribution, so I think the safe bet
would be to build Qt, but only the modules you need by yourself
with that option, then building PySide only for those modules,
and then packaging your app, or wait
Hello again, I've been able to get rid of the izma issues by building on a
arm mac, that somehow improved things but they still complain about these 2:
Symbols: _responsibility_get_pid_responsible_for_pid,
_responsibility_spawnattrs_setdisclaim
I found this ticket:
Hello Cristián, thanks for the reply. So are these symbols from python
rather than Qt?
I'll ask in another forum, thanks!
On Mon, Mar 27, 2023 at 3:56 PM Cristián Maureira-Fredes via PySide <
pyside@qt-project.org> wrote:
> Hey Pedro,
>
> thanks for reaching out on this.
>
> There are a couple
Hey Pedro,
thanks for reaching out on this.
There are a couple of symbols that are guarded by the dev build of Qt
https://codereview.qt-project.org/c/qt/qtbase/+/437376
But many of the others, like
_lzma_stream_encoder, _lzma_alone_decoder, etc
are present in CPython while building
