Re: [Development] "qtLibraryTarget" output changed from Qt 5.3.2 to Qt 5.4.0
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 < > 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 qt4 > > > behavior. > > > > > > > Would you like me to log a bug? > > > well, why not. > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] "qtLibraryTarget" output changed from Qt 5.3.2 to Qt 5.4.0
On Fri, Feb 20, 2015 at 01:07:07PM +0200, William Hallatt wrote: > On 20 February 2015 at 11:58, Oswald Buddenhagen > wrote: > > i presume the right approach would be admitting defeat, making a new > > internal function for qt, and restoring qtLibraryTarget() to its qt4 > > behavior. > > > > Would you like me to log a bug? > well, why not. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] "qtLibraryTarget" output changed from Qt 5.3.2 to Qt 5.4.0
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 project file was auto-generated by the QtCreator project template. > however, all our plugin-related examples are littered with references to > it, so it would be a bit hard to sweep it under the rug. > i presume the right approach would be admitting defeat, making a new > internal function for qt, and restoring qtLibraryTarget() to its qt4 > behavior. > Would you like me to log a bug? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] "qtLibraryTarget" output changed from Qt 5.3.2 to Qt 5.4.0
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 was wondering if it is > documented anywhere that one should NOT use "Qt" tags when writing plugins > (or for anything else for that matter)? > > The way I see it, this is either a bug, or it should be explicitly stated > in the documentation (provided that it isn't somewhere I haven't found) > that one shouldn't do it as this took me hours to resolve. > technically speaking, the function isn't documented at all and should be considered internal. however, all our plugin-related examples are littered with references to it, so it would be a bit hard to sweep it under the rug. i presume the right approach would be admitting defeat, making a new internal function for qt, and restoring qtLibraryTarget() to its qt4 behavior. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
