[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyQt] ANN: pyqtdeploy v1.3 Released
From: David Cortesi <davecortesi () gmail ! com>
Date: 2016-06-15 16:05:41
Message-ID: CALyzANtZ02gNewdwVvGvX1QP=WSeEr3odErgRKCmHtfTP6gPDw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Not to do with wheels. All to do with creating a working MacOS app from a
(Py)Qt5 program that calls on QWebEngine.
However, looking at the Pyqtdeploy about page,
>... Qt's qmake tool is used to generate a platform-specific Makefile which
will then generate a single executable. Further Qt and/or platform specific
tools can then be used to convert the executable to a platform specific
deployable package.
So it would be those "further" tools, specifically macdeployqt (
http://doc.qt.io/qt-5/osx-deployment.html) that would be required. I had
fondly hoped that pyqtdeploy had picked up that part, but understandable
that not.
> I have not been following pyqtdeploy for some time. Does it now support
> QWebEngine deployment in MacOS? (that is, does it do the complicated
> relocation of QWebEngine components into the Frameworks and Resources
> sub-folders of an app folder, with alterations of the module link paths?)
>
> What's that got to do with pyqtdeploy? That sort of stuff is related to
> creating wheels.
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div><font size="2"><span \
style="font-family:arial,helvetica,sans-serif"><br><br></span></font></div><font \
size="2"><span style="font-family:arial,helvetica,sans-serif">Not to do with wheels. \
All to do with creating a working MacOS app from a (Py)Qt5 program that calls on \
QWebEngine.<br><br></span></font></div><font size="2"><span \
style="font-family:arial,helvetica,sans-serif">However, looking at the Pyqtdeploy \
about page, <br><br>><span \
style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;lette \
r-spacing:normal;line-height:20.8px;text-align:start;text-indent:0px;text-transform:no \
ne;white-space:normal;word-spacing:0px;display:inline!important;float:none">...</span><span \
style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;lette \
r-spacing:normal;line-height:20.8px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none"> \
Qt's<span class=""> </span></span><span \
style="margin:0px;color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:n \
ormal;letter-spacing:normal;line-height:20.8px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">qmake</span><span \
style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;lette \
r-spacing:normal;line-height:20.8px;text-align:start;text-indent:0px;text-transform:no \
ne;white-space:normal;word-spacing:0px;display:inline!important;float:none"><span \
class=""> </span>tool is used to generate a platform-specific<span class=""> \
</span></span><span style="margin:0px;color:rgb(0,0,0);font-style:normal;font-variant: \
normal;font-weight:normal;letter-spacing:normal;line-height:20.8px;text-align:start;te \
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Makefile</span><span \
style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;lette \
r-spacing:normal;line-height:20.8px;text-align:start;text-indent:0px;text-transform:no \
ne;white-space:normal;word-spacing:0px;display:inline!important;float:none"><span \
class=""> </span>which will then generate a single executable. Further Qt and/or \
platform specific tools can then be used to convert the executable to a platform \
specific deployable package.<br><br></span></span></font></div><font size="2"><span \
style="font-family:arial,helvetica,sans-serif"><span \
style="color:rgb(0,0,0);font-style:normal;font-variant:normal;font-weight:normal;lette \
r-spacing:normal;line-height:20.8px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none">So \
it would be those "further" tools, specifically macdeployqt (<a \
href="http://doc.qt.io/qt-5/osx-deployment.html">http://doc.qt.io/qt-5/osx-deployment.html</a>) \
that would be required. I had fondly hoped that pyqtdeploy had picked up that part, \
but understandable that not.<br><br></span></span></font><div><div><div><div><div \
class="gmail_extra"><font size="2"><span \
style="font-family:arial,helvetica,sans-serif"><br></span></font><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div \
class="h5"><font size="2"><span style="font-family:arial,helvetica,sans-serif"> > \
I have not been following pyqtdeploy for some time. Does it now support QWebEngine \
deployment in MacOS? (that is, does it do the complicated relocation of QWebEngine \
components into the Frameworks and Resources sub-folders of an app folder, with \
alterations of the module link paths?)<br></span></font> <font size="2"><span \
style="font-family:arial,helvetica,sans-serif"><br></span></font> </div></div><font \
size="2"><span style="font-family:arial,helvetica,sans-serif">What's that got to \
do with pyqtdeploy? That sort of stuff is related to creating wheels.<span \
class=""></span><br></span></font></blockquote></div></div></div></div></div></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic