Done.
https://bugreports.qt.io/browse/QTBUG-44595
Have a good weekend!
On 20 February 2015 at 13:22, Oswald Buddenhagen
oswald.buddenha...@theqtcompany.com wrote:
On Fri, Feb 20, 2015 at 01:07:07PM +0200, William Hallatt wrote:
On 20 February 2015 at 11:58, Oswald Buddenhagen
On Fri, Feb 20, 2015 at 01:07:07PM +0200, William Hallatt wrote:
On 20 February 2015 at 11:58, Oswald Buddenhagen
oswald.buddenha...@theqtcompany.com wrote:
i presume the right approach would be admitting defeat, making a new
internal function for qt, and restoring qtLibraryTarget() to its
On 20 February 2015 at 11:58, Oswald Buddenhagen
oswald.buddenha...@theqtcompany.com wrote:
technically speaking, the function isn't documented at all and should be
considered internal.
I would never have known of its existence if it wasn't for the fact that
the code I referenced from my
Good day everyone,
I upgraded from Qt 5.3.2 to Qt 5.4.0 yesterday and suddenly found that my
QML plugin imports no longer worked. It turned out that the reason for
this is the qtLibraryTarget output generation seems to have changed from
Qt5.3.x to Qt 5.4.0 in that it now automatically adds a 5
On Fri, Feb 20, 2015 at 10:49:21AM +0200, William Hallatt wrote:
TARGET = QtQmlComponents
TARGET = $$qtLibraryTarget($$TARGET)
Which, for 5.3.x gave me QtQmlComponents.dll (on Windows obviously), but
for 5.4 now gives me Qt5QmlComponents.dll.
I understand that this is an edge case, but I
