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 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
[Development] "qtLibraryTarget" output changed from Qt 5.3.2 to Qt 5.4.0
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" to any TARGET value that starts with "Qt" In other words, in my plugin .pro, I have the following code: TEMPLATE = lib TARGET = QtQmlComponents QT += qml quick CONFIG += qt plugin TARGET = $$qtLibraryTarget($$TARGET) Which, for 5.3.x gave me "QtQmlComponents.dll" (on Windows obviously), but for 5.4 now gives me "Qt5QmlComponents.dll". This broke absolutely everything. 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. Opinions? Regards, William. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] GIMP QML exporter script (project not on Gerrit)
Hi Tuukka, No, it wasn't that at all, the documentation is what saved me. My problem stemmed from having committed a whole bunch of changes and then having to "retro-fit" Change-Id's etc (which meant a git learning curve for me) since I didn't initially consider making any changes (i.e. my git environment wasn't set up as per the "Setting up Gerrit" instructions). Had I not ended up in a situation where I had to work "back to front", it would have gone a lot more smoothly. The only recommendation I have at the moment is perhaps to improve on the qtrepotools documentation (if it exists, I haven't been able to find it) and perhaps a pre-commit hook (I do not know if such a thing is possible) that could do some sanitizing up front? Thanks again for a spectacular framework! Kind regards, William. On 9 January 2015 at 09:35, Turunen Tuukka wrote: > > Thanks, William. > > If some of the instructions were misleading, hard to find or inadequate, > please let us know. Intention is to make it straightforward to contribute. > In addition to your contribution we value your feedback for improving the > instructions. > > Yours, > > > Tuukka > > From: William Hallatt > Date: Friday 9 January 2015 07:02 > To: William Hallatt > Cc: "development@qt-project.org" > Subject: Re: [Development] GIMP QML exporter script (project not on > Gerrit) > > Thanks for all the assistance folks. Finally managed to submit to > Gerrit and sort out all the sanity bot's reviews :) > > Have a good weekend, > William. > > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] GIMP QML exporter script (project not on Gerrit)
Thanks for all the assistance folks. Finally managed to submit to Gerrit and sort out all the sanity bot's reviews :) Have a good weekend, William. On 8 January 2015 at 07:37, William Hallatt wrote: > Shot, thanks Robert! I'm making progress. > > Kind regards. > William. > > On 7 January 2015 at 16:40, Robert Löhning < > robert.loehn...@theqtcompany.com> wrote: > >> Hi William, >> >> you can let the commit-msg hook do that for you, see >> http://qt-project.org/wiki/Setting-up-Gerrit >> >> Best Regards, >> Robert >> >> >> Am 07.01.2015 um 14:56 schrieb William Hallatt: >> > Hi Jens, >> > >> > That is exactly what I did (amongst some other, minor syntactic and >> layout >> > stuff). >> > >> > Feel free to have a look: >> > https://github.com/goblincoding/qt-labs-gimp-qmlexporter >> > >> > For now I am battling to figure out how to add Change-Id's with 'git >> rebase >> > -i' so that I can push to Gerrit...so far no luck (it is a bit of a >> > learning curve for me, my git exposure to date has involved little more >> > than pushing, pulling and committing to my own personal repo's). >> > >> > Thanks so much for the epic work you did on this script! It has saved >> me a >> > lot of pain and suffering. >> > >> > Kind regards, >> > William. >> > >> > >> > >> > On 7 January 2015 at 13:49, wrote: >> > >> >> I would actually be curious as to what functionality you are planning >> on >> >> adding aside from obviously updating it to Qt 5. The main reason I >> >> abandoned the plugin 5 years ago was the lack of support for grouped >> layers >> >> in Gimp at the time. I know this is no longer an issue so it should be >> >> possible to use layer groups in order to create and keep a hierarchy >> of QML >> >> items now. At least this would make it significantly better suited for >> QML >> >> exports. >> >> >> >> Regards, >> >> Jens >> >> >> >> >> >> On 07 Jan 2015, at 10:42, William Hallatt >> wrote: >> >> >> >> Thanks for the replies! I am making progress...now to figure out how >> to >> >> get the Change-Id's in after the fact... :) >> >> >> >> On 7 January 2015 at 10:42, Liang Qi wrote: >> >> >> >>> I guess you mean this on github, >> >>> https://github.com/qtproject/qt-labs-gimp-qmlexporter >> >>> >> >>> Then please contribute to >> >>> >> https://codereview.qt-project.org/#/admin/projects/qt-labs/gimp-qmlexporter >> >>> >> >>> Good luck! >> >>> >> >>> Regards, >> >>> Liang >> >>> >> >>> On 7 January 2015 at 08:33, William Hallatt >> >>> wrote: >> >>> >> >>>> Good day, >> >>>> >> >>>> I forked and made some changes to Jens Bache-Wiig's original QML >> >>>> exporter script (GIMP only) on GitHub and was wondering if I could >> simply >> >>>> create a pull request for my changes? >> >>>> >> >>>> I have searched for the project on Gerrit, but it does not seem to >> exist >> >>>> there. >> >>>> >> >>>> Advice would be appreciated. >> >>>> >> >>>> Kind regards, >> >>>> William Hallatt >> >>>> >> >> -- >> Robert Löhning, Software Engineer | The Qt Company >> >> Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin >> Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der >> Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB >> 144331 B >> >> Email: robert.loehn...@theqtcompany.com | Mobile: + 49 151 1634 9248 | >> Phone: +49 30 63 92 3255 www.qt.io |Qt Blog: http://blog.qt.digia.com/ | >> Twitter: @QtbyDigia, @Qtproject | Facebook: www.facebook.com/qt >> ___ >> 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] GIMP QML exporter script (project not on Gerrit)
Shot, thanks Robert! I'm making progress. Kind regards. William. On 7 January 2015 at 16:40, Robert Löhning wrote: > Hi William, > > you can let the commit-msg hook do that for you, see > http://qt-project.org/wiki/Setting-up-Gerrit > > Best Regards, > Robert > > > Am 07.01.2015 um 14:56 schrieb William Hallatt: > > Hi Jens, > > > > That is exactly what I did (amongst some other, minor syntactic and > layout > > stuff). > > > > Feel free to have a look: > > https://github.com/goblincoding/qt-labs-gimp-qmlexporter > > > > For now I am battling to figure out how to add Change-Id's with 'git > rebase > > -i' so that I can push to Gerrit...so far no luck (it is a bit of a > > learning curve for me, my git exposure to date has involved little more > > than pushing, pulling and committing to my own personal repo's). > > > > Thanks so much for the epic work you did on this script! It has saved > me a > > lot of pain and suffering. > > > > Kind regards, > > William. > > > > > > > > On 7 January 2015 at 13:49, wrote: > > > >> I would actually be curious as to what functionality you are planning on > >> adding aside from obviously updating it to Qt 5. The main reason I > >> abandoned the plugin 5 years ago was the lack of support for grouped > layers > >> in Gimp at the time. I know this is no longer an issue so it should be > >> possible to use layer groups in order to create and keep a hierarchy of > QML > >> items now. At least this would make it significantly better suited for > QML > >> exports. > >> > >> Regards, > >> Jens > >> > >> > >> On 07 Jan 2015, at 10:42, William Hallatt > wrote: > >> > >> Thanks for the replies! I am making progress...now to figure out how to > >> get the Change-Id's in after the fact... :) > >> > >> On 7 January 2015 at 10:42, Liang Qi wrote: > >> > >>> I guess you mean this on github, > >>> https://github.com/qtproject/qt-labs-gimp-qmlexporter > >>> > >>> Then please contribute to > >>> > https://codereview.qt-project.org/#/admin/projects/qt-labs/gimp-qmlexporter > >>> > >>> Good luck! > >>> > >>> Regards, > >>> Liang > >>> > >>> On 7 January 2015 at 08:33, William Hallatt > >>> wrote: > >>> > >>>> Good day, > >>>> > >>>> I forked and made some changes to Jens Bache-Wiig's original QML > >>>> exporter script (GIMP only) on GitHub and was wondering if I could > simply > >>>> create a pull request for my changes? > >>>> > >>>> I have searched for the project on Gerrit, but it does not seem to > exist > >>>> there. > >>>> > >>>> Advice would be appreciated. > >>>> > >>>> Kind regards, > >>>> William Hallatt > >>>> > > -- > Robert Löhning, Software Engineer | The Qt Company > > Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin > Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der > Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB > 144331 B > > Email: robert.loehn...@theqtcompany.com | Mobile: + 49 151 1634 9248 | > Phone: +49 30 63 92 3255 www.qt.io |Qt Blog: http://blog.qt.digia.com/ | > Twitter: @QtbyDigia, @Qtproject | Facebook: www.facebook.com/qt > ___ > 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] GIMP QML exporter script (project not on Gerrit)
Hi Jens, That is exactly what I did (amongst some other, minor syntactic and layout stuff). Feel free to have a look: https://github.com/goblincoding/qt-labs-gimp-qmlexporter For now I am battling to figure out how to add Change-Id's with 'git rebase -i' so that I can push to Gerrit...so far no luck (it is a bit of a learning curve for me, my git exposure to date has involved little more than pushing, pulling and committing to my own personal repo's). Thanks so much for the epic work you did on this script! It has saved me a lot of pain and suffering. Kind regards, William. On 7 January 2015 at 13:49, wrote: > I would actually be curious as to what functionality you are planning on > adding aside from obviously updating it to Qt 5. The main reason I > abandoned the plugin 5 years ago was the lack of support for grouped layers > in Gimp at the time. I know this is no longer an issue so it should be > possible to use layer groups in order to create and keep a hierarchy of QML > items now. At least this would make it significantly better suited for QML > exports. > > Regards, > Jens > > > On 07 Jan 2015, at 10:42, William Hallatt wrote: > > Thanks for the replies! I am making progress...now to figure out how to > get the Change-Id's in after the fact... :) > > On 7 January 2015 at 10:42, Liang Qi wrote: > >> I guess you mean this on github, >> https://github.com/qtproject/qt-labs-gimp-qmlexporter >> >> Then please contribute to >> https://codereview.qt-project.org/#/admin/projects/qt-labs/gimp-qmlexporter >> >> Good luck! >> >> Regards, >> Liang >> >> On 7 January 2015 at 08:33, William Hallatt >> wrote: >> >>> Good day, >>> >>> I forked and made some changes to Jens Bache-Wiig's original QML >>> exporter script (GIMP only) on GitHub and was wondering if I could simply >>> create a pull request for my changes? >>> >>> I have searched for the project on Gerrit, but it does not seem to exist >>> there. >>> >>> Advice would be appreciated. >>> >>> Kind regards, >>> William Hallatt >>> >>> ___ >>> Development mailing list >>> Development@qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/development >>> >>> >> >> >> -- >> http://www.qiliang.net >> > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > > > -- > > Jens Bache-Wiig > http://www.cutehacks.com > Cross Platform Apps and Services > > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] GIMP QML exporter script (project not on Gerrit)
Please ignore previous email, I found it (for some or other reason it did not appear in search). Thanks! On 7 January 2015 at 09:33, William Hallatt wrote: > Good day, > > I forked and made some changes to Jens Bache-Wiig's original QML exporter > script (GIMP only) on GitHub and was wondering if I could simply create a > pull request for my changes? > > I have searched for the project on Gerrit, but it does not seem to exist > there. > > Advice would be appreciated. > > Kind regards, > William Hallatt > -- Don't do anything you can't undo unless you know what you can't do once you've done it. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] GIMP QML exporter script (project not on Gerrit)
Thanks for the replies! I am making progress...now to figure out how to get the Change-Id's in after the fact... :) On 7 January 2015 at 10:42, Liang Qi wrote: > I guess you mean this on github, > https://github.com/qtproject/qt-labs-gimp-qmlexporter > > Then please contribute to > https://codereview.qt-project.org/#/admin/projects/qt-labs/gimp-qmlexporter > > Good luck! > > Regards, > Liang > > On 7 January 2015 at 08:33, William Hallatt > wrote: > >> Good day, >> >> I forked and made some changes to Jens Bache-Wiig's original QML exporter >> script (GIMP only) on GitHub and was wondering if I could simply create a >> pull request for my changes? >> >> I have searched for the project on Gerrit, but it does not seem to exist >> there. >> >> Advice would be appreciated. >> >> Kind regards, >> William Hallatt >> >> ___ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development >> >> > > > -- > http://www.qiliang.net > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] GIMP QML exporter script (project not on Gerrit)
Good day, I forked and made some changes to Jens Bache-Wiig's original QML exporter script (GIMP only) on GitHub and was wondering if I could simply create a pull request for my changes? I have searched for the project on Gerrit, but it does not seem to exist there. Advice would be appreciated. Kind regards, William Hallatt ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QtQuick/QtGui/QtCore leak on exit
Hi everyone, I have a QtQuick app (that links against external MS MFC libraries) that triggers memory leak warnings on exit. I have run the test app through both Dr Memory as well as BoundsChecker (both in VS 2008) and both report memory leaks stemming from the QtQuick and QtCore libraries. The only related information I have been able to find is this: http://doc.qt.digia.com/solutions/4/qtwinmigrate/winmigrate-walkthrough.html#a-note-about-mfc-s-memory-leak-detection Which (1) is not completely relevant to my situation and (2) might be outdated information. Could I safely assume that these are false positives? I am not overly concerned since the leaks are tiny and only on exit, but the object dump to stdout is a bit annoying. Unfortunately the best I can do is to attach the results file from Dr Memory. I'm happy to provide additional information if required (excluding source). Kind regards, William Hallatt Dr. Memory version 1.8.0 build 8 built on Sep 9 2014 16:27:02 Dr. Memory results for pid 4152: "test.exe" Application cmdline: "C:\QtDev\test\test\Deploy\test.exe" Recorded 108 suppression(s) from default C:\DrMemory\bin\suppress-default.txt Error #1: UNINITIALIZED READ: reading register eflags replace_memcmp d:\drmemory_package\drmemory\replace.c(777): libGLESv2d.dll!rx::Renderer9::setViewport c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\renderer\d3d9\renderer9.cpp(1141): libGLESv2d.dll!gl::Context::applyRenderTarget c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\context.cpp(1733): libGLESv2d.dll!gl::Context::clear c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\context.cpp(1943): libGLESv2d.dll!glClear c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\libglesv2.cpp(870): Qt5Quickd.dll!QSGBindable::clear c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgrenderer.cpp(79): Qt5Quickd.dll!QSGBatchRenderer::Renderer::renderBatches c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgbatchrenderer.cpp(2246): Qt5Quickd.dll!QSGBatchRenderer::Renderer::render c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgbatchrenderer.cpp(2433): Qt5Quickd.dll!QSGRenderer::renderScene c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgrenderer.cpp(261): Qt5Quickd.dll!QSGRenderer::renderScene c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgrenderer.cpp(220): Qt5Quickd.dll!QSGRenderContext::renderNextFrame c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\qsgcontext.cpp(356): Qt5Quickd.dll!QQuickWindowPrivate::renderSceneGraph c:\qt\qt5build\qtdeclarative\src\quick\items\qquickwindow.cpp(386): Qt5Quickd.dll!QSGWindowsRenderLoop::renderWindow c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\qsgwindowsrenderloop.cpp(458): Qt5Quickd.dll!QSGWindowsRenderLoop::render c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\qsgwindowsrenderloop.cpp(398): Qt5Quickd.dll!QSGWindowsRenderLoop::exposureChanged c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\qsgwindowsrenderloop.cpp(315): Qt5Quickd.dll!QQuickWindow::exposeEvent c:\qt\qt5build\qtdeclarative\src\quick\items\qquickwindow.cpp(216): Qt5Guid.dll!QWindow::event c:\qt\qt5build\qtbase\src\gui\kernel\qwindow.cpp(1956): Qt5Quickd.dll!QQuickWindow::event c:\qt\qt5build\qtdeclarative\src\quick\items\qquickwindow.cpp(1348): Qt5Cored.dll!QCoreApplicationPrivate::notify_helper c:\qt\qt5build\qtbase\src\corelib\kernel\qcoreapplication.cpp(1052): Qt5Cored.dll!QCoreApplication::notify c:\qt\qt5build\qtbase\src\corelib\kernel\qcoreapplication.cpp(997): Error #2: UNINITIALIZED READ: reading register eax libGLESv2d.dll!rx::Renderer9::setViewport c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\renderer\d3d9\renderer9.cpp(1141): libGLESv2d.dll!gl::Context::applyRenderTarget c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\context.cpp(1733): libGLESv2d.dll!gl::Context::clear c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\context.cpp(1943): libGLESv2d.dll!glClear c:\qt\qt5build\qtbase\src\3rdparty\angle\src\libglesv2\libglesv2.cpp(870): Qt5Quickd.dll!QSGBindable::clear c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgrenderer.cpp(79): Qt5Quickd.dll!QSGBatchRenderer::Renderer::renderBatches c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgbatchrenderer.cpp(2246): Qt5Quickd.dll!QSGBatchRenderer::Renderer::render c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgbatchrenderer.cpp(2433): Qt5Quickd.dll!QSGRenderer::renderScene c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgrenderer.cpp(261): Qt5Quickd.dll!QSGRenderer::renderScene c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\coreapi\qsgrenderer.cpp(220): Qt5Quickd.dll!QSGRenderContext::renderNextFrame c:\qt\qt5build\qtdeclarative\src\quick\scenegraph\qsgcontext.cpp(356): Qt5Quickd.dll!QQuickWindowPrivate::renderScen
Re: [Development] www.qt.io/download-open-source is broken
On 18 September 2014 09:07, Knoll Lars wrote: > The automatic download is a bit overdone currently, as it also downloads > on back/forward navigations and doesn’t remember that the package has > already been downloaded once. So we should consider whether that’s the > best approach or whether an approach more similar to the old download page > is better. It’s one more click, but then it’s very explicit, and people > will get exactly the package they asked for. Although one could probably argue that users should be paying attention to what they're doing, the "re-download" on navigation could potentially have a nasty side-effect. Many Qt users (myself included) live in countries where access to uncapped bandwidth is not a given and it could mean a nasty internet bill if you accidentally trigger an additional download that pushes you over your cap (e.g. many of my colleagues have 3 - 5 GB monthly caps so an extra ~700MB obviously makes a big difference). Perhaps just something to consider :) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCreator, non-Qt project, GCC and C++11 - Apologies for sending to wrong list
Morning everybody,
Yesterday was obviously not my day, apologies for sending the below to this
list.
On 2 June 2014 16:13, William Hallatt wrote:
> Sorry, just realised that something went really wobbly in that loop copy
> and paste of mine, should be:
>
> int x[10] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 };
>
> for( auto i : x )
> {
>int bob = 0;
> }
>
>
> On 2 June 2014 13:27, William Hallatt wrote:
>
>> Hi everybody,
>>
>> Trying to set up a non-Qt project compatible with C++11 and using GCC,
>> but QtCreator keeps highlighting C++11 syntax with messages such as "auto'
>> is a C++11 extension".
>>
>> I am confident that my kits are set up correctly (building Qt
>> applications that use C++11 works fine). For the non-Qt project I am
>> trying, I have tried various combinations of adding
>>
>> CONFIG += c++11
>>
>> and/or
>>
>> QMAKE_CXXFLAGS += -std=c++11
>>
>> but no luck.
>>
>> GCC 4.7.3, Ubuntu 12.04, Qt 5.3, QtCreator 3.1.1 (for Linux 64 bit).
>>
>> FYI, I literally only created a new, non-Qt C++ project and have not
>> added any files, nor changed the .pro other than in the above manner. The
>> only code I added to the generated main.cpp is
>>
>> for( auto x : 10 )
>> {
>>int bob = 0;
>> }
>>
>> Your help would be greatly appreciated.
>> William.
>>
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCreator, non-Qt project, GCC and C++11
Sorry, just realised that something went really wobbly in that loop copy
and paste of mine, should be:
int x[10] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 };
for( auto i : x )
{
int bob = 0;
}
On 2 June 2014 13:27, William Hallatt wrote:
> Hi everybody,
>
> Trying to set up a non-Qt project compatible with C++11 and using GCC, but
> QtCreator keeps highlighting C++11 syntax with messages such as "auto' is a
> C++11 extension".
>
> I am confident that my kits are set up correctly (building Qt applications
> that use C++11 works fine). For the non-Qt project I am trying, I have
> tried various combinations of adding
>
> CONFIG += c++11
>
> and/or
>
> QMAKE_CXXFLAGS += -std=c++11
>
> but no luck.
>
> GCC 4.7.3, Ubuntu 12.04, Qt 5.3, QtCreator 3.1.1 (for Linux 64 bit).
>
> FYI, I literally only created a new, non-Qt C++ project and have not added
> any files, nor changed the .pro other than in the above manner. The only
> code I added to the generated main.cpp is
>
> for( auto x : 10 )
> {
>int bob = 0;
> }
>
> Your help would be greatly appreciated.
> William.
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
[Development] QtCreator, non-Qt project, GCC and C++11
Hi everybody,
Trying to set up a non-Qt project compatible with C++11 and using GCC, but
QtCreator keeps highlighting C++11 syntax with messages such as "auto' is a
C++11 extension".
I am confident that my kits are set up correctly (building Qt applications
that use C++11 works fine). For the non-Qt project I am trying, I have
tried various combinations of adding
CONFIG += c++11
and/or
QMAKE_CXXFLAGS += -std=c++11
but no luck.
GCC 4.7.3, Ubuntu 12.04, Qt 5.3, QtCreator 3.1.1 (for Linux 64 bit).
FYI, I literally only created a new, non-Qt C++ project and have not added
any files, nor changed the .pro other than in the above manner. The only
code I added to the generated main.cpp is
for( auto x : 10 )
{
int bob = 0;
}
Your help would be greatly appreciated.
William.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Categorized logging inside Qt
That is exactly what I thought the C was for... On 11 April 2014 13:07, Jędrzej Nowacki wrote: > On Friday 11 of April 2014 08:31:41 Rutledge Shawn wrote: > > On 11 Apr 2014, at 10:11 AM, Poenitz Andre wrote: > > > shawn.rutle...@digia.com wrote: > > >> On 10 Apr 2014, at 7:20 PM, Frederik Gladhorn wrote: > > >>> Hi all, > > >>> > > >>> I just started to port accessibility to the new and shiny categorized > > >>> logging. > > >>> > http://blog.qt.digia.com/blog/2014/03/11/qt-weekly-1-categorized-loggin > > >>> g/ > > >>> > > >>> I'd propose we decide on a certain style of declaring categories. > > >>> > > >>> A quick grep shows that we already have some variety, I'd like to > unify > > >>> this before Qt 5.3 is out of the door. I actually saw a patch adding > > >>> DBG_FOOBAR as new category, that made me wonder about which style we > > >>> should use.>> > > >> I think the pattern is OK though: all uppercase, with a prefix like > DBG > > >> and try to keep them as short as possible since they get repeated all > > >> over. > > > > > > We tend to avoid abbreviations, so DBG instead of DEBUG looks odd. > > > > > > Your reasoning that it's REPEATED ALL OVER also MAKES ME THINK > > > that USING ALL CAPS might be NO GOOD IDEA as it gives ME the > > > feeling the code is constantly SHOUTING AT ME. > > > > Not having all caps would be fine, but I still think they should be > short, > > and don't see a problem with abbreviations because the context is > obvious; > > it doesn't obscure the meaning like making a member variable or function > > name too short would do. qCDebug is already an abbreviation for "Qt > > categorized logging of the debug variety". > > ___ > > Development mailing list > > Development@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development > > Hi, > > So 'C' in qCDebug is for "categorized", I thought that it is for > "C-like". > Abbreviations in code are wrong, please try to avoid them. Meaning is > obvious > for you, because you already knew the meaning, for a newcomer it is not > that > trivial. > > Cheers, > Jędrek > ___ > 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] Qt 5.1 Beta Released
Congratulations to everybody involved, things are moving really quickly and I'm very happy to count myself among the 500 000 (!!!) Qt users :) Regards, William Hallatt On 14 May 2013 13:10, Turunen Tuukka wrote: > > Link to blog should be: > http://blog.qt.digia.com/blog/2013/05/14/qt-5-1-beta-released/ > > Yours, > > Tuukka > > > > From: Tuukka Turunen > Date: tiistai 14. toukokuuta 2013 14.06 > To: "development@qt-project.org" > Subject: Qt 5.1 Beta Released > > > Hi All, > > We have now released Qt 5.1 Beta as agreed in the release team meeting > yesterday. > > See: http://blog.qt.digia.com/blog/2013/05/08/qt-5-1-beta-released/ > > Now let's get the final pieces in place and 5.1.0 final out before > summer. > > Yours, > > Tuukka > > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > > -- Don't do anything you can't undo unless you know what you can't do once you've done it. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
