> On May 10, 2015, at 9:08 PM, mark diener wrote:
>
> Well, it looks like the big weakness in OSX deployment is macdeployqt and we
> are on version 5.4.1+
>
> I was able to change my macdeployqt command line FROM:
>
> macdeployqt ./testdep.app/ -qmldir=/macdev/qdev/testdep/ -verbose=2
>
>
André Somers schreef op 11-5-2015 om 08:26:
> Bo Thorsen schreef op 10-5-2015 om 09:43:
>> You are aware of http://doc.qt.io/qt-5/qquickpainteditem.html, right?
>> This makes it pretty trivial to port painter based items to QtQ2.
>>
> Did you actually read the use case? I am rendering both custom a
Bo Thorsen schreef op 10-5-2015 om 09:43:
>
> You are aware of http://doc.qt.io/qt-5/qquickpainteditem.html, right?
> This makes it pretty trivial to port painter based items to QtQ2.
>
Did you actually read the use case? I am rendering both custom and
standard elements to QPainter based devices
On Sat, May 9, 2015, at 11:41 PM, Alan Alpert wrote:
> > Can we declare the module in Deprecated state and keep bug compatibility
> > with
> > previous versions? If people are using it to transition from Qt 4, it should
> > retain as much of Qt 4's behaviour as possible. That includes buggy
> > b
Well, it looks like the big weakness in OSX deployment is macdeployqt and
we are on version 5.4.1+
I was able to change my macdeployqt command line FROM:
macdeployqt ./testdep.app/ -qmldir=/macdev/qdev/testdep/ -verbose=2
TO:
macdeployqt testdep.app/ -qmldir=/macdev/qdev/testdep/ -verbose=2
Hello:
Has someone gotten macdeployqt to actually work and create a self running
bundle
that successfully runs on OSX ?
If yes, please share your command line for macdeployqt.
My macdeployqt command line:
macdeployqt ./testdep.app/ -qmldir=/macdev/qdev/testdep/
my otool dump of the bundle aft
Thiago A. Corrêa wrote:
> IMHO you should not use Qt Quick 2D Renderer as an argument unless it were
> available in the open source package, but you could argue that there is
> mesa software render support in 5.5. What's the difference between the 2?
>
> export QMLSCENE_DEVICE=softwarecontext
> an
Simon Hausmann wrote:
> Yes, this isn't perfect, because we still include large quantities of code
> in src/3rdparty in Qt that has unprotected calls to getenv(). But then
> that hasn't stopped us from patching that code in the past.
That will not help on distributions using system copies of third
Marc Mutz wrote:
> Tests are presumably easy. If everything else fails, QtTest could execute
> itself anew for each test. After a quick scan, the only thing I'm worried
> about in QtBase is qglxconvenience.cpp, which temporarily modifies the
> environment.
That would be my code. The environment is
Den 05-05-2015 kl. 09:24 skrev Kojo Tero:
> Hello!
>
> The call for papers to the Qt World Summit has been opened.
>
> We welcome you to share your insight, experience and inspiration at our
> 12th annual Qt event.
>
> For details on the themes and instructions for submitting your
> abstracts, plea
Den 08-05-2015 kl. 14:44 skrev André Somers:
> Frederik Gladhorn schreef op 8-5-2015 om 14:39:
>> Hi,
>>
>> I think the dust has settled quite a bit and the declarative module is
>> becoming better by the day. We have seen it evolve and the new Java Script
>> engine is running smoothly (and activel
11 matches
Mail list logo
