QML apps not runnable using static build up to Qt 5.0.1 release!
-
wrote on 18 Mar 2013, 07:41 last edited by
4 months have passed.... 5.0.1 has been released almost two months ago... There are no any solutions... ((
-
wrote on 18 Mar 2013, 07:45 last edited by
I assume that you're using the commercial license if you're using static linking. If so, maybe send an email to Tukka Turunen or another person in Digia, with details of your exact problem. Unfortunately, I don't know much about how static linkage would affect the various plugins to the QML core, to be able to offer any suggestions.
The other possibility is to ping aalpert on #qt-qml freenode as he is maintainer of the QtDeclarative module now.
Cheers,
Chris. -
wrote on 18 Mar 2013, 08:21 last edited by
At the moment i'm trying to test Qt 5 open-source version for my personal testing purposes with simple "Hello World" QML apps.
I look closely to Qt for a long time and i want to convince my company management to migrate to Qt 5 and QtQuick framework from Embarcadero RAD Studio (aka Borland, VCL) purchasing Qt commercial licence for future development. And the only thing that i can't explain to them is impossibility of creating standalone QML-applications, consisting of one executable file as it was possible before with RAD Studio... -
wrote on 18 Mar 2013, 09:28 last edited by
[quote author="chrisadams" date="1363592752"]I assume that you're using the commercial license if you're using static linking. If so...[/quote]
What if not?
-
wrote on 19 Mar 2013, 00:30 last edited by
If you're not using the commercial version, all I can suggest is upvoting the bug report, so that it is more likely to get attention quicker than if it wasn't upvoted, and also asking Alan about it on IRC.
If you are intending to use the commercial version, and you are evaluating it with that specific purpose in mind, then I really suggest sending an email to Tukka Turunen with your query, as he is probably the best person to talk to about this matter.
Cheers,
Chris. -
wrote on 9 Apr 2013, 12:29 last edited by
Any news on this issue? According to the bug tracker, this bug is scheduled for fix in 5.0.2, but I tried 5.0.2-rc1, and it still cannot use QtQuick2 when statically built… :-(
-
wrote on 9 Apr 2013, 13:44 last edited by
Yes, already Qt 5.1 alpha is available http://blog.qt.digia.com/blog/2013/04/08/qt-5-1-alpha-available/, but it's total silence on this global bug.
I wait for fix very long time too...
May be fix is difficult but there are only 4 votes in the bugreport at the moment and fix-priority is too low for the Devs?Somebody else, who interested in the fix, please vote for it in the bugreport!
https://bugreports.qt-project.org/browse/QTBUG-28357 -
wrote on 9 Apr 2013, 17:49 last edited by
Don't worry, issues with dozens of votes doesn't seem to be in a rush as well.
-
wrote on 3 May 2013, 12:11 last edited by
Avassen: I have the same issue with you. I voted :)
-
wrote on 19 May 2013, 08:54 last edited by
I stumbled upon it, too.
I also wrote to the mailing list... I really hope it will be fixed in 5.1.0 -
wrote on 27 Feb 2014, 22:31 last edited by
To take this one step further, it doesn't seem you can use a static build of qt with Qt5Widgets and the QtQuickLayoutsPlugin. It generates already defined linker erros in vs2012.
Is this suppose to be the case?
-
wrote on 2 Jun 2014, 10:57 last edited by
The problem is actual for QT version 5.3
-
wrote on 14 Apr 2015, 08:16 last edited by
The problem is actual for QT version 5.4