Re: [Development] Revisiting high-DPI configuration options
On 7/20/16, 5:12 AM, "Development on behalf of Edward Welbourne"wrote: > >Then again, our SVG support is embarrassingly poor, Especially when it doesn’t support clip path. Which I imagine will be vital for icon designs. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtWebKit is coming back
I don’t see Mac mentioned in either links provided. Is Mac supported? Stephen Chu On 6/4/16, 3:20 PM, "Development on behalf of Konstantin Tokarev" <development-bounces+stephen.chu=mathworks@qt-project.org on behalf of annu...@yandex.ru> wrote: >Hi all, > >As some of you may already know, there is an ongoing effort to revive QtWebKit >by updating its WebKit engine to the current state of upstream at webkit.org >[1]. > >While it still haven't reached feature parity with QtWebkit module hosted by >Qt Project, its Widgets API is already in a good shape [2]. It also brings >many new features, including support for large part of ES2015. It is binary >compatible with QtWebKit 5.6 and can be used as drop-in replacement. > >In this regard I have following questions to the Qt community: > >1. Would you like to see this project as a part of Qt Project? > >QtWebKit used to be a part of Qt Essentials (at least before its removal in >5.6 release, I'm not sure what status does it have right now). I think it's >neither feasible nor reasonable to restore this status it as a part of Qt >Essentials, as it used to be before 5.6. We have a massive amount of 3rd party >code so it would require much more work to support complete range of platforms >and compilers, supported by Qt. In particular, full C++ 11 support is required >from compiler, making minimal required GCC version as high as 4.8. (In the >meanwhile, WebKit already started adoption of C++1y in trunk, though GCC 4.9 >is still supported) > >Also it's likely that supported platforms won't have perfect feature parity, >and it's not clear if we are going to support WebKit 2 on Windows at all (if >somebody reading this is interested, please join us!) > >2. Is it OK to use "QtWebKit" name for this project, and if yes, how should it >be versioned? > >Pros: >* It is a drop-in replacement for QtWebKit, so it would simplify its >downstream adoption, e.g. Linux distros could replace old insecure QtWebKit >5.6 with this new offering. >* QtWebKit is a name of Qt port of WebKit. This project is basically a rebase >of Qt port code to the newer revision of trunk, so I don't see it as a fork of >original project, but mere update. > >Cons: >* Old QtWebKit will probably continue to exist, because range of supported >platforms for new QtWebKit is more limited. Right now we have no plans to >support Android, QNX or WinCE, it's also unclear if we will ever support >WebKit 2 on Windows. That means we need a way to make a clear difference >between branches of the project. >* Users may mistakenly report problems specific to the new version to Qt JIRA. >This issue could be worked around if Qt Project kindly allowed us to have a >project in Qt JIRA (maybe even resurrect old QTWEBKIT product), so I could >simply move such reports to another project and reassign. OTOH, it's quite >possible that bugs reported against new QtWebKit affect 5.6 as well, for >example see QTBUG-53532. > >Of course, if anybody here is interested, any kind of help will be greatly >appreciated. > >Thanks in advance! > > >[1] https://github.com/annulen/webkit/wiki >[2] https://lists.webkit.org/pipermail/webkit-qt/2016-May/004062.html >Latest development is in "qtwebkit-stable" branch, we are planning to release >TP2 with many fixes and improvements really soon > >-- >Regards, >Konstantin >___ >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] Proposal: New list of Qt 5 reference / Tier 1 platforms
On 11/14/12 8:37 AM, Sorvig Morten wrote: 10.6 is separate issue. It is getting less relevant, but still has a significant market share (31%)[0]. I would say it's a bit to early to drop it. Also 10.6 supports 32-bit machines. If 10.6 is still officially supported, so should 32-bit on 10.6. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 mingw build trying to link against Qt5Cored0.dll
I ran into this error while trying to build Qt 5 from git with mingw: mingw32-make[3]: Entering directory 'C:/Qt/5.0/qtbase/src/network' mingw32-make -f Makefile.Debug all mingw32-make[4]: Entering directory 'C:/Qt/5.0/qtbase/src/network' g++ -shared -Wl,--out-implib,C:\Qt\5.0\qtbase\lib\libQt5Networkd.a -o ..\..\lib\ Qt5Networkd.dll object_script.Qt5Networkd.Debug -lws2_32 -ldnsapi -ladvapi32 -L C:/Qt/5.0/qtbase/lib -lQt5Cored0 tmp\obj\debug_shared\Qt5Networkd_resource_res.o c:/mingw/bin/../lib/gcc/i686-w64-mingw32/4.7.2/../../../../i686-w64-mingw32/bin/ ld.exe: cannot find -lQt5Cored0 It seems to be looking for Qt5Cored0.dll instead of Qt5Cored.dll. Maybe some bug introduced by the lib renaming? This is from qt5 git, not the latest qtbase. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Heads up for Windows devs: ANGLE landing soon
On 11/2/12 4:19 AM, Koehne Kai wrote: -Original Message- From: development-bounces+kai.koehne=digia@qt-project.org [mailto:development-bounces+kai.koehne=digia@qt-project.org] On Behalf Of Stephen Chu Sent: Thursday, November 01, 2012 9:08 PM To: jason.bar...@outlook.com Cc: development@qt-project.org Subject: Re: [Development] Heads up for Windows devs: ANGLE landing soon On 10/23/12 4:26 AM, Jason Barron wrote: This is just a heads up for people developing Qt on Windows. We will shortly add a copy of the ANGLE project into the Qt 3rdparty tree and make it the default OpenGL configuration if no other option is given. If you're not familiar with ANGLE, you can read about it here: http://code.google.com/p/angleproject/ You need to have the DirectX SDK installed to build ANGLE. It works on MSVC and MinGW (both 32-bit and 64-bit). If you would prefer to continue using desktop OpenGL, then simply pass -opengl desktop to configure and you should get the same behavior as before. The change on Gerrit is here: https://codereview.qt-project.org/#change,37290 I'm working on updating the installation and deployment docs as well as writing a blog post to give some more details. Regards, Jason ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development I tried to build Qt 5 from git with mingw and ended up with this error: Project ERROR: Cannot determine DirectX SDK location. Please set DXSDK_DIR environment variable. I thought a copy of angle library is included? Or do we need to install DirectX SDK from now on? ANGLE is based on the DirectX SDK. While Mingw-w64 ships the appropriate headers, it's apparently missing the runtime library (d3dcompiler AFAIR) and the fxc.exe effect compiler from the Direct X SDK, used at compile time. So yes, right now you've to either install a Direct X SDK, or pass -opengl desktop . (I'm also worried that these dependencies break crosscompiling... we should really consider including pre-generated files here instead of relying on fxc.exe being available at compile time). Regards Kai Thanks. I will try -opengl desktop since I don't use opengl in my Windows projects. But which DirectX SDK version is required? I have Windows SDK 7.1 installed but it doesn't seem to have those files you mentioned. I downloaded DirectX SDK (June 2010) and it failed to install on my Windows 7 X64 box. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] Qt5: Problem connecting QTimer::timeout() to lambda
On 11/1/12 1:17 PM, Thiago Macieira wrote: On quinta-feira, 1 de novembro de 2012 13.03.56, Stephen Chu wrote: I find out what QPrivateSignal is for but it's not clear if lambda can still be used to connect to such private signals. If I connect QTimer::timeout() to a slot that takes no argument, it compiles fine. But when I try to connect to a lambda function without any argument, the results in the mentioned error. Can you rephrase and/or give us code samples? takes no arguments and without any argument are semantically the same in English. This doesn't work (compile error): QTimer timer; QObject::connect(timer, QTimer::timeout, [=](){}); This does: QTimer timer; auto label = new QLabel; QObject::connect(timer, QTimer::timeout, label, QWidget::show); Again. This is using clang 3.1 with QMAKE_CXXFLAGS += -std=c++11 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Heads up for Windows devs: ANGLE landing soon
On 10/23/12 4:26 AM, Jason Barron wrote: This is just a heads up for people developing Qt on Windows. We will shortly add a copy of the ANGLE project into the Qt 3rdparty tree and make it the default OpenGL configuration if no other option is given. If you're not familiar with ANGLE, you can read about it here: http://code.google.com/p/angleproject/ You need to have the DirectX SDK installed to build ANGLE. It works on MSVC and MinGW (both 32-bit and 64-bit). If you would prefer to continue using desktop OpenGL, then simply pass -opengl desktop to configure and you should get the same behavior as before. The change on Gerrit is here: https://codereview.qt-project.org/#change,37290 I'm working on updating the installation and deployment docs as well as writing a blog post to give some more details. Regards, Jason ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development I tried to build Qt 5 from git with mingw and ended up with this error: Project ERROR: Cannot determine DirectX SDK location. Please set DXSDK_DIR environment variable. I thought a copy of angle library is included? Or do we need to install DirectX SDK from now on? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] Qt5: Problem connecting QTimer::timeout() to lambda
On 11/1/12 4:13 PM, Thiago Macieira wrote: On quinta-feira, 1 de novembro de 2012 14.49.27, Stephen Chu wrote: Again. This is using clang 3.1 with QMAKE_CXXFLAGS += -std=c++11 Is that the real clang 3.1, or the 3.1 version of Apple clang? They are not the same, they have different C++11 support status and known bugs. I am sorry for not being clear. It's mainline (real) 3.1. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] Qt5: Problem connecting QTimer::timeout() to lambda
On 11/1/12 4:28 PM, Thiago Macieira wrote: On quinta-feira, 1 de novembro de 2012 13.13.34, Thiago Macieira wrote: On quinta-feira, 1 de novembro de 2012 14.49.27, Stephen Chu wrote: Again. This is using clang 3.1 with QMAKE_CXXFLAGS += -std=c++11 Is that the real clang 3.1, or the 3.1 version of Apple clang? They are not the same, they have different C++11 support status and known bugs. The code was expected to work. We need to figure out if it's a compiler bug or whether the C++ standard says it shouldn't work. Bug reported: https://bugreports.qt-project.org/browse/QTBUG-27813 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 QMessageBox doesn't respond?
I find the problem is caused by this commit: http://qt.gitorious.org/qt/qtbase/commit/595deca5c909d99a8cd157b9fb6c82c64b1db1f5 Backing it out fixes the problem. The bug is closed for not reproducible. But I built and ran Qt 5 on different Macs (10.7 and 10.8) and they also show the same hanging problem. And I do believe the problem is real. Can some running Qt 5 on Mac verify it? Thanks. On 10/14/12 10:29 AM, Stephen Chu wrote: On 10/11/12 12:06 PM, Stephen Chu wrote: I am wondering if this is the result of switching qtbase to master instead of staying wiht qt5. When I call this on a Mac: QMessageBox::warning(NULL, , warning!); The dialog shows up but clicking at the OK button doesn't dismiss it. And QMessageBox code is taking 100% of a core spinning. Before I file a bug report, can someone with latest qtbase (from yesterday) try this? Thanks. Qt 5 git started to get update again. And I now confirm the QMessageBox is broken on Mac: https://bugreports.qt-project.org/browse/QTBUG-27562 ___ 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 QMessageBox doesn't respond?
On 10/11/12 12:06 PM, Stephen Chu wrote: I am wondering if this is the result of switching qtbase to master instead of staying wiht qt5. When I call this on a Mac: QMessageBox::warning(NULL, , warning!); The dialog shows up but clicking at the OK button doesn't dismiss it. And QMessageBox code is taking 100% of a core spinning. Before I file a bug report, can someone with latest qtbase (from yesterday) try this? Thanks. Qt 5 git started to get update again. And I now confirm the QMessageBox is broken on Mac: https://bugreports.qt-project.org/browse/QTBUG-27562 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 QMessageBox doesn't respond?
I am wondering if this is the result of switching qtbase to master instead of staying wiht qt5. When I call this on a Mac: QMessageBox::warning(NULL, , warning!); The dialog shows up but clicking at the OK button doesn't dismiss it. And QMessageBox code is taking 100% of a core spinning. Before I file a bug report, can someone with latest qtbase (from yesterday) try this? Thanks. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Build Qt 5 in 32-bit with mingw-builds 4.7.2
I just installed mingw-build 4.7.2 on Windows 7 64-bit. I then configured Qt 5 this way: configure -developer-build -opensource -confirm-license -nomake tests -nomake examples -c++11 The built libraries are in 64-bit. How do I configure Qt 5 to build 32-bit libs? Thanks. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] No recent commit in qt5 git?
The last commit in http://qt.gitorious.org/qt/qt5 was a week ago. Is it frozen for release? I just saw https://codereview.qt-project.org/#change,36732 has been merged and wanted to try it but can't since it's not in Qt 5 yet. I think I can bring qtbase to head for that. But last time I did it, I had to wipe my whole Qt5 repo to get back to qt5 current. Maybe I will have better luck this time. :) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] No recent commit in qt5 git?
On 10/10/12 3:59 PM, Thiago Macieira wrote: On quarta-feira, 10 de outubro de 2012 15.01.56, Stephen Chu wrote: The last commit in http://qt.gitorious.org/qt/qt5 was a week ago. Is it frozen for release? No. It's blocked on failing tests. Help fix them and it will go in sooner :-) I will probably make it worse. I just saw https://codereview.qt-project.org/#change,36732 has been merged and wanted to try it but can't since it's not in Qt 5 yet. Check out master in qtbase and pull. Thanks. Will do that. I think I can bring qtbase to head for that. But last time I did it, I had to wipe my whole Qt5 repo to get back to qt5 current. Maybe I will have better luck this time. :) Just ask on IRC how to get back. But you don't need to get back, it's fine to run later versions of code. I do that all the time. Ya. But you are not just anybody. :) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Really bad graphics view text rendering in Qt 5 on Mac
So the problem went away after a reboot during weekend and the bug is thus marked as invalid. However another commenter indicated it's happening on his Mac too. I just retried the example and sure enough the problem shows up again. Can people running Qt 5 on Mac try the example in the report and see if it's happening too? Thanks. On 9/28/12 4:03 PM, Stephen Chu wrote: Just reported this bug: https://bugreports.qt-project.org/browse/QTBUG-27386 Regardless of currently scaling factor, QGraphicsTextItem seems to be rendered onto a back buffer with the same resolution as the screen before copied onto the painting surface. ___ 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
[Development] Using lambda in QtConcurrent::map
I am having problem using lambda in QtConcurrent::map() function. The following code: #include QtConcurrent int foo(int i) { return i+1; } void moo(QListint list) { QtConcurrent::mapped(list, [](int i){ return foo(i); }); } produces errors below with Clang 3.1. Is lambda supported in map()? Or do I need to wrap the lambda in a std::function? clang++ -c -pipe -mmacosx-version-min=10.6 -arch i386 -stdlib=libc++ -std=c++11 -g -gdwarf-2 -Wall -W -fPIE -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_CONCURRENT_LIB -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/Qt/5.0/qtbase/mkspecs/macx-clang-libc++-32 -I../../Dropbox/Client2012 -I../../Dropbox/Client2012/DataTable -I../../Dropbox/Client2012/Tools -I../../Dropbox/Client2012/OUTViewer -I../../Dropbox/Client2012/OUTViewer/lcms -I../../Dropbox/Client2012/OUTViewer/lcms/lcms2-2.4/include -I../../Dropbox/Client2012 -I/Qt/5.0/qtbase/include -I/Qt/5.0/qtbase/include/QtPrintSupport -I/Qt/5.0/qtbase/include/QtWidgets -I/Qt/5.0/qtbase/include/QtConcurrent -I/Qt/5.0/qtbase/include/QtNetwork -I/Qt/5.0/qtbase/include/QtGui -I/Qt/5.0/qtbase/include/QtCore -I. -I/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers -I/System/Library/Frameworks/AGL.framework/Headers -I. -F/Qt/5.0/qtbase/lib -o moo.o ../../Dropbox/Client2012/Tools/moo.cpp In file included from ../../Dropbox/Client2012/Tools/moo.cpp:1: In file included from /Qt/5.0/qtbase/include/QtConcurrent/QtConcurrent:11: In file included from /Qt/5.0/qtbase/include/QtConcurrent/qtconcurrentfilter.h:1: In file included from /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentfilter.h:49: In file included from /Qt/5.0/qtbase/include/QtConcurrent/qtconcurrentfilterkernel.h:1: In file included from /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentfilterkernel.h:50: In file included from /Qt/5.0/qtbase/include/QtConcurrent/qtconcurrentmapkernel.h:1: /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentmapkernel.h:166:78: error: no type named 'result_type' in 'lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29' class MappedEachKernel : public IterateKernelIterator, typename MapFunctor::result_type ~^~~ /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentmapkernel.h:214:33: note: in instantiation of template class 'QtConcurrent::MappedEachKernelQListint::const_iterator, lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29 ' requested here struct SequenceHolder1 : public Base ^ /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentmapkernel.h:238:34: note: in instantiation of template class 'QtConcurrent::SequenceHolder1QListint, QtConcurrent::MappedEachKernelQListint::const_iterator, lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29 , lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29 ' requested here return startThreadEngine(new SequenceHolderType(sequence, functor)); ^ /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentmap.h:182:12: note: in instantiation of function template specialization 'QtConcurrent::startMappedvoid, QListint, lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29 ' requested here return startMappedtypename QtPrivate::MapResultTypevoid, MapFunctor::ResultType(sequence, QtPrivate::createFunctionWrapper(map)); ^ ../../Dropbox/Client2012/Tools/moo.cpp:7:2: note: in instantiation of function template specialization 'QtConcurrent::mappedQListint, lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29 ' requested here QtConcurrent::mapped(list, [](int i){ return foo(i); }); ^ In file included from ../../Dropbox/Client2012/Tools/moo.cpp:1: In file included from /Qt/5.0/qtbase/include/QtConcurrent/QtConcurrent:11: In file included from /Qt/5.0/qtbase/include/QtConcurrent/qtconcurrentfilter.h:1: In file included from /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentfilter.h:49: In file included from /Qt/5.0/qtbase/include/QtConcurrent/qtconcurrentfilterkernel.h:1: In file included from /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentfilterkernel.h:50: In file included from /Qt/5.0/qtbase/include/QtConcurrent/qtconcurrentmapkernel.h:1: /Qt/5.0/qtbase/include/QtConcurrent/../../src/concurrent/qtconcurrentmapkernel.h:169:34: error: no type named 'result_type' in 'lambda at ../../Dropbox/Client2012/Tools/moo.cpp:7:29' typedef typename MapFunctor::result_type T; ~^~~ 2 errors generated. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5: Warning using QImage as QtConcurrent::mapped return type
The following code generates warning about memcpy on object type: QListQImage images; QListQImage future = QtConcurrent::blockingMapped(images, scaled); The warning: In file included from /Qt/5.0/qtbase/include/QtCore/qvector.h:1: /Qt/5.0/qtbase/include/QtCore/../../src/corelib/tools/qvector.h:459:56: warning: source of this 'memcpy' call is a pointer to dynamic class 'QImage'; vtable pointer will be copied [-Wdynamic-class-memaccess] ::memcpy(static_castvoid *(dst), srcBegin, (srcEnd - srcBegin) * sizeof(T)); ^ It seems that Qt thinks QImage is a POD type? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Really bad graphics view text rendering in Qt 5 on Mac
Just reported this bug: https://bugreports.qt-project.org/browse/QTBUG-27386 Regardless of currently scaling factor, QGraphicsTextItem seems to be rendered onto a back buffer with the same resolution as the screen before copied onto the painting surface. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Really bad graphics view text rendering in Qt 5 on Mac
On 9/28/12 4:03 PM, Stephen Chu wrote: Just reported this bug: https://bugreports.qt-project.org/browse/QTBUG-27386 Regardless of currently scaling factor, QGraphicsTextItem seems to be rendered onto a back buffer with the same resolution as the screen before copied onto the painting surface. Oh. This is interesting. It seems that if the item is transformed with scale factor of 5 or higher, the text is rendered properly: https://bugreports.qt-project.org/secure/attachment/29438/textrender.png ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] What's with bugreports.qt-project.org?
On 9/26/12 6:44 AM, Shaw Andy wrote: I am just going to specifically refer to this part in my capacity as Head of Support at Digia. But the support team (myself included) do strive to fix bugs or provide workarounds, we have a good track record in this respect. It is as a result of customers reporting bugs to us that we are able to fix some bugs sooner than it may happen by going via the bug tracker at bugreports.qt-project.org. This is because the support team's priorities are for the customers first so we deal with what they are bringing to our attention. Granted not everything is fixed, but I can assure you that it does make a difference to be a customer and report things to us. I am a bit curious on the fixes by Digia for the paying customers. Do those fixes go to the LGPL sources? Or do they remain privileges of Digia's customers? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Releasing] Beta 2 release
On 9/22/12 4:55 PM, Jiang Jiang wrote: Hi, On Thu, Sep 20, 2012 at 9:05 PM, Stephen Chu step...@ju-ju.com wrote: And also this one for consideration: https://bugreports.qt-project.org/browse/QTBUG-27198 At least this issue is fixed by 75cd2dec71d81868e1c4d5df32eb602faeb165fc. Looks like automatic mouse grabbing is the culprit of many widget bugs. - Jiang I rebuild Qt 5 from git and indeed it's no longer an issue. Thanks. BTW. What was the automatic mouse grabbing intended for? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Releasing] Beta 2 release
On 9/23/12 9:18 AM, Stephen Chu wrote: On 9/22/12 4:55 PM, Jiang Jiang wrote: Hi, On Thu, Sep 20, 2012 at 9:05 PM, Stephen Chu step...@ju-ju.com wrote: And also this one for consideration: https://bugreports.qt-project.org/browse/QTBUG-27198 At least this issue is fixed by 75cd2dec71d81868e1c4d5df32eb602faeb165fc. Looks like automatic mouse grabbing is the culprit of many widget bugs. - Jiang I rebuild Qt 5 from git and indeed it's no longer an issue. Thanks. BTW. What was the automatic mouse grabbing intended for? FYI: https://bugreports.qt-project.org/browse/QTBUG-26598 is still there. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Releasing] Beta 2 release
On 9/20/12 8:45 AM, Knoll Lars wrote: To be able to understand the quality of the beta better, we will need some help from everybody. Have a look at the Qt 5 bug statistics at https://bugreports.qt-project.org/secure/Dashboard.jspa?selectPageId=11712 . As you can see we currently have very few Blockers (P1) and only some P1's. But there are close to 400 bugs in there that aren't yet evaluated. It would be good if all Maintainers and Approvers could help and do their share to evaluate these bugs, so that we better know what remains to be done for the second beta. Once that's done, further work should focus around fixing the high priority bugs found. I am not a maintainer but I like to nominate this bug as a blocker: https://bugreports.qt-project.org/browse/QTBUG-27221 And also this one for consideration: https://bugreports.qt-project.org/browse/QTBUG-27198 The event handling on Mac is pretty messed up and these two are probably both the result of it. I don't think Qt 5 is shippable, at lease on Mac, before this is sorted out. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] ExtendedSelection in 5.0 has no effect on Mac OS X
OK. Here's the show stopper: https://bugreports.qt-project.org/browse/QTBUG-27221 It works on Windows build. :( ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 4.8 clang and libc++
On 9/10/12 4:21 PM, Sylvain Pointeau wrote: and now I have this error: In file included from kernel/qvariant.cpp:64: In file included from ../../include/QtCore/5.0.0/QtCore/private/qvariant_p.h:1: ../../include/QtCore/5.0.0/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:248:33: error: base 'SelfTestFinal1' is marked 'final' struct Derived : public T, public FallbackMixin {}; // - ... ^ ../../include/QtCore/5.0.0/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:252:86: note: in instantiation of member class 'QVariantIsNullanonymous::CoreTypesFilter::HasIsNullMethodQVariantIsNullanonymous::CoreTypesFilter::SelfTestFinal1, true::Derived' requested here ...No test(TypeCheckbool (FallbackMixin::*)() const, C::isNull *); What's the version of your clang? I am using MacPorts Clang 3.1 and never have this error. In fact, I just rebuilt Qt 5 from latest git and other than qbasicatomic.h (which should be fixed with clang 3.2) and qmacstyle_mac.mm (CGFloat size is different in 32-bit), I don't have any error to deal with. Although I don't build webkit. This is my configure line if it helps: ./configure -developer-build -opensource -confirm-license -nomake examples -nomake tests -c++11 -platform macx-clang-libc++-32 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 4.8 clang and libc++
On 9/8/12 9:55 AM, Olivier Goffart wrote: On Saturday 08 September 2012 15:42:20 Sylvain Pointeau wrote: clang-libc++ is the only way to have C++11 on mac os x No. The other way was mentioned already in this thread. no, you need to link with libc++ to have the library support for c++11. You can also get recent GCC's libstdc++ I tried GCC 4.7 (via MacPorts) to build Qt 5 a couple of months ago and it didn't go well. Mainly some Apple-ism in the system headers and compiler flags. Basically building GUI apps with non-Apple GCC can be really trying. On the other hand, non-Apple Clang 3.1 (again via MacPorts) with the new macx-clang-libc++ mkspec in Qt 5 works really well. MacPorts Clang doesn't have the 10.7 minimum requirement when using -stdlib=libc++ flag. Now I don't know if the same applies to Qt 4.8 but MacPorts Clang should make it a bit easier. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build Qt 5 with MinGW 4.7?
On 8/27/12 4:28 AM, marius.storm-ol...@nokia.com wrote: You can use the git dir/cmd in your path instead. That way you have no extra msys tools in your path and the git.bat will add the required paths locally upon execution. So you get full git functionality without polluting you path. Cool. Thanks for the tip. Much appreciated. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build Qt 5 with MinGW 4.7?
On 8/26/12 10:03 AM, Stephen Chu wrote: Thanks for pointing out the build differences. I didn't realize there are so many different builds of the same MinGW version. Switching to mingw-builds get me further. But then I got this error: cp qmake.exe C:\Qt\5.0\qtbase\bin\qmake.exe g++: error: tmp/obj/debug_shared/arch.o: No such file or directory mingw32-make: *** [arch.exe] Error 1 Could not find output file: No such file or directory *** qtbase/configure exited with non-zero status. I went to qtbase\config.text\arch and manually ran mingw32-make to create the obj file in question. Then re-run configure and it worked. OK. I figured out that this error is caused by git in my PATH. I think sh.exe in git\bin is causing configure some issues. Removing git from PATH and configure finished without issue. qt5_tool requires git in PATH so I'll just have to remember changing PATH back and forth between clean up/update and configure. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Build Qt 5 with MinGW 4.7?
I am trying to build Qt 5 from git using MinGW 4.7. It fails at bootstrapping configure: C:\Qt\5.0configure -developer-build -opensource -confirm-license + C:/Qt/5.0/qtbase/configure -developer-build -opensource -confirm-license Please wait while bootstrapping configure ... ... ... QtDBus: created headers.pri file mingw32-make: Interrupt/Exception caught (code = 0xc005, addr = 0x0040aff9) *** qtbase/configure exited with non-zero status. Any idea why or how can I troubleshoot this? Thanks. PS. I need 4.7 for C+11 support. I am using Clang 3.1 on Mac and need to match the 2 compilers' C+11 support as much as possible. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 4.8 clang and libc++
On 8/24/12 4:06 PM, Sylvain Pointeau wrote: On Fri, Aug 24, 2012 at 9:59 PM, Thiago Macieira thiago.macie...@intel.com mailto:thiago.macie...@intel.com wrote: On sexta-feira, 24 de agosto de 2012 19.11.14, Sylvain Pointeau wrote: Hi, I would like to compile Qt 4.8 using clang / libc++ (to have c++11) is it possible? No one has ever reported success. Then again, no one has ever reported failure either -- no one has ever reported trying. I did: ./configure -no-qt3support -platform unsupported/macx-clang unfortunately it doesn't use libc++ I am ready to try, but how should I configure it? otherwise, I am also ready to migrate to Qt5 Going Qt5 will make your life a lot easier. Make sure you use macx-clang-libc++ mkspec. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QVairant::Type enums are now obsolete?
I just noticed that all the QVariant::Type enums are now marked as obsolete in 5.0 doc: http://qt-project.org/doc/qt-5.0/qvariant-obsolete.html#Type-enum The goal seems to be to switch to QMetaType enums. But in the attempt to make my code up-to-date, I find that strait replace of the old names with the new can be very problematic. For example the following 2 lines of code produce different variants: QVariant v1(QMetaType::QString); QVariant v2(QVariant::String); v1 is a int with value 10 and v2 is a QString with empty content. It seems a QVariant constructor that takes a QMetaType::Type is needed. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Error building Qt 5 with clang in 32-bit
I tried to build Qt 5 (from git) with MacPorts clang 4.7 using macx-clang-libc++-32 mkspec. It failed with narrowing errors like this: styles/qmacstyle_mac.mm:3828:45: error: non-constant-expression cannot be narrowed from type 'qreal' (aka 'double') to 'CGFloat' (aka 'float') in initializer list [-Wc++11-narrowing] CGFloat colorComp[] = { textColor.redF(), textColor.greenF(), ^~~~ Building in 64-bit works since CGFloat is defined as double in x64, but it's float in 32-bit. Anyway I can work around this? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Announce] Qt Creator 2.5.1 released
On 7/25/12 8:23 AM, List for announcements regarding Qt releases and development wrote: We just released Qt Creator 2.5.1 ! Blog: http://labs.qt.nokia.com/2012/07/25/qt-creator-2-5-1-released/ Download: http://qt-project.org/wiki/Qt_Creator_Releases Br, The Qt Creator Team The debug helper fails to build on Mac with Qt 5. Replacing dumpper.cpp from git master fixes it. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Qt-creator] Designer: Buddy checkbox disables OK button?
On 7/23/12 1:54 PM, Stephen Chu wrote: I was adding rows to a form layout and find that once I checked the Buddy checkbox, the OK button became disabled: http://i.imgur.com/j6cth.png Is this intended? How do I set the pair to be buddies then? This is with Creator 2.5.1 built from git pull on OS X 10.7.4. So I figured out that this is a Designer issue, not Creator since Creator only builds a plugin that load Designer. Cross over to development list. After diving into Designer source, I find out I need the have a so-called buddy marker which is a '' in the label text. After including that, the buddy checkbox automatically checked. I can't find any mention of the buddy mark anywhere. Why do we need that in the label? And why does buddy check rely on it? I can still specify buddy relation with buddy edit mode WITHOUT the marker in the label. So why is it required? And if it's required for good reason, the buddy check box should be disable since it's always linked to the existence of the marker. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Using Qt 5 with C++11/Clang 3.1?
On 7/7/12 4:32 PM, Thiago Macieira wrote: On sábado, 7 de julho de 2012 11.17.58, Stephen Chu wrote: /Qt/5.0/qtbase/include/QtCore/../../src/corelib/global/qflags.h:51:7: note: 'QFlag' is not literal because it is not an aggregate and has no constexpr constructors other than copy or move constructors class QFlag ^ Adding Q_DECL_CONSTEXPR to QFlag constructor fixes it: Q_DECL_CONSTEXPR inline QFlag(int i); I don't know if if is another Clang bug. No, that looks like a real issue, Please submit the patch for the QFlag constexpr constructor. I couldn't setup my Mac right to submit patch. Some SSH issue I can't figure out how to get around. But I see it's been fixed a couple days ago. So thank whoever patched it. I also updated MacPorts clang 3.2 to a later version containing the fix for the constructor issue and it compiles without modifying the code. However, 3.2 (trunk 160101) generates the following warning: /Qt/5.0/qtbase/include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:613:49: warning: field is uninitialized when used here [-Wuninitialized] inline QWeakPointer(X *ptr, bool) : d(ptr ? d-getAndRef(ptr) : 0), value(ptr) ^ The warning makes sense to me on the appearance. Don't know enough about internal stuffs to be sure though. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Qt-creator] No headers in Mac frameworks?
On 7/10/12 9:28 AM, eike.zil...@nokia.com wrote: On 10 Jul 2012, at 15:19, ext Stephen Chu wrote: On 7/10/12 5:41 AM, Stephen Kelly wrote: On Monday, July 09, 2012 18:11:30 Stephen Chu wrote: On 7/9/12 6:03 PM, Shawn Rutledge wrote: On 9 July 2012 22:25, Stephen Chu step...@ju-ju.com wrote: On 7/9/12 3:53 PM, Stephen Chu wrote: On 7/9/12 3:18 PM, Stephen Chu wrote: I built Qt 5 from git on Mac with -developer-build option and find there's no link to headers in the resulted frameworks. There are only symlinks to the libs but not headers like in Qt 4.8. Qt Creator editor has trouble finding the headers with this setup. This makes finding definitions of Qt types almost impossible. It still compiles and builds fine. Just the editor failing to find them. OK. I removed and re-add Qt5 install to Creator and now it finds the headers. Don't know what happened. :) Scrap that. It still doesn't work. I hit one of the framework which I manually added a symlink to the include folder. Sorry for the back and forth. I believe it's an issue in Qt 5 build script. I've seen an issue like that a month or so ago, but then it got fixed. Which module is it? Er. All of them. Ossi is (hopefully :)) working on generating the includes in the build dir instead of the source dir. That might fix your issue too. thread.gmane.org/gmane.comp.lib.qt.devel/4855/focus=4926 Thanks. I will watch for the fix. But that issue seems to focus on non-qtbase modules. What I have is none of the frameworks has any header installed within them. Not even QtCore. This sounds like the same issue as in the thread Creator doesn't like my local Qt 5 build? on the qt-creator mailing list, where Ossi claims that it should be fixed in Qt Creator master? Br, Just pulled and built Creator from git. Still doesn't work without the symlinks in the frameworks. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Qt-creator] No headers in Mac frameworks?
On 7/9/12 3:53 PM, Stephen Chu wrote: On 7/9/12 3:18 PM, Stephen Chu wrote: I built Qt 5 from git on Mac with -developer-build option and find there's no link to headers in the resulted frameworks. There are only symlinks to the libs but not headers like in Qt 4.8. Qt Creator editor has trouble finding the headers with this setup. This makes finding definitions of Qt types almost impossible. It still compiles and builds fine. Just the editor failing to find them. OK. I removed and re-add Qt5 install to Creator and now it finds the headers. Don't know what happened. :) Scrap that. It still doesn't work. I hit one of the framework which I manually added a symlink to the include folder. Sorry for the back and forth. I believe it's an issue in Qt 5 build script. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Qt-creator] No headers in Mac frameworks?
On 7/9/12 6:03 PM, Shawn Rutledge wrote: On 9 July 2012 22:25, Stephen Chu step...@ju-ju.com wrote: On 7/9/12 3:53 PM, Stephen Chu wrote: On 7/9/12 3:18 PM, Stephen Chu wrote: I built Qt 5 from git on Mac with -developer-build option and find there's no link to headers in the resulted frameworks. There are only symlinks to the libs but not headers like in Qt 4.8. Qt Creator editor has trouble finding the headers with this setup. This makes finding definitions of Qt types almost impossible. It still compiles and builds fine. Just the editor failing to find them. OK. I removed and re-add Qt5 install to Creator and now it finds the headers. Don't know what happened. :) Scrap that. It still doesn't work. I hit one of the framework which I manually added a symlink to the include folder. Sorry for the back and forth. I believe it's an issue in Qt 5 build script. I've seen an issue like that a month or so ago, but then it got fixed. Which module is it? Er. All of them. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Using Qt 5 with C++11/Clang 3.1?
Has anyone successfully build Qt 5 to use with Clang 3.1 on any platform? I see the new macx-clang-libc++ mkspecs are now included. Using it enables automatic detection of C++11 features in configure. But that causes errors on C++11 features when building like: animation/qabstractanimation.cpp:215:1: error: initialization of non-aggregate type 'QBasicAtomicPointerQThreadStorageQUnifiedTimer * ' with an initializer list Q_GLOBAL_STATIC(QThreadStorageQUnifiedTimer *, unifiedTimer) ^~ /Qt/5.0/qtbase/src/corelib/../../include/QtCore/../../src/corelib/global/qglobal.h:768:33: note: expanded from macro 'Q_GLOBAL_STATIC' = { Q_BASIC_ATOMIC_INITIALIZER(0), false }; \ ^ /Qt/5.0/qtbase/src/corelib/../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:256:41: note: expanded from macro 'Q_BASIC_ATOMIC_INITIALIZER' # define Q_BASIC_ATOMIC_INITIALIZER(a) { (a) } ^~~ I can get it sort of built by configuring with -no-c++11 option. It still fails to build some of the libraries but it's enough for my simple project. But the same errors (and constexpr ones I reported before) show up whenever -std=c++11 and moc is involved. GCC 4.7 seems to be able to compile those fine but I read that it's actually bugs in the compiler. And we are stuck with 4.2 on OS X anyways. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Using Qt 5 with C++11/Clang 3.1?
On 7/6/12 1:22 PM, Stephen Chu wrote: On 7/6/12 12:19 PM, Thiago Macieira wrote: On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote: #if defined(Q_COMPILER_CONSTEXPR) defined(Q_COMPILER_DEFAULT_MEMBERS) defined(Q_COMPILER_DELETE_MEMBERS) fixes the problem for me. So it should be disabled for those broken version of clang. Looks like a compiler bug for me, or we forgot one Q_COMPILER macro. We might So this error is caused by bugs in Clang 3.1? need to introduce Q_COMPILER_UNIFORM_INITIALIZATION. Isn't that Q_COMPILER_INITIALIZER_LISTS? BTW. Please don't disable initializer lists for Clang 3.1. That's one major reason why I opt for 3.1 instead of 3.0. :) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Using Qt 5 with C++11/Clang 3.1?
On 7/6/12 2:25 PM, Thiago Macieira wrote: On sexta-feira, 6 de julho de 2012 13.22.38, Stephen Chu wrote: On 7/6/12 12:19 PM, Thiago Macieira wrote: On sexta-feira, 6 de julho de 2012 18.12.10, Olivier Goffart wrote: #if defined(Q_COMPILER_CONSTEXPR) defined(Q_COMPILER_DEFAULT_MEMBERS) defined(Q_COMPILER_DELETE_MEMBERS) fixes the problem for me. So it should be disabled for those broken version of clang. Looks like a compiler bug for me, or we forgot one Q_COMPILER macro. We might So this error is caused by bugs in Clang 3.1? I don't know. I need someone who has the compiler to test that it's implementing the features correctly. need to introduce Q_COMPILER_UNIFORM_INITIALIZATION. Isn't that Q_COMPILER_INITIALIZER_LISTS? No. Uniform initialisation is like this: struct Foo { Foo(int, const char *); }; Foo f = { 1, hello }; ICC: Line 6: error: initialization with {...} is not allowed for object of type Foo Foo f = { 1, hello }; ^ Clang 3.0: stdin:6:5: error: non-aggregate type 'Foo' cannot be initialized with an initializer list Foo f = { 1, hello }; ^ ~~ If I remove the equal sign, GCC still compiles and Clang produces the same error message, but ICC says: Line 6: error: no default constructor exists for class Foo Foo f { 1, hello }; ^ Line 6: error: expected a ; Foo f { 1, hello }; ^ So Clang seems to support the feature partially, but will not call the constructor. Thanks for the explanation. I got confused, again. :) I tried Clang 3.1 and it compiles with or without the equal sign. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Using Qt 5 with C++11/Clang 3.1?
On 7/6/12 3:23 PM, Thiago Macieira wrote: On sexta-feira, 6 de julho de 2012 14.53.56, Stephen Chu wrote: I tried Clang 3.1 and it compiles with or without the equal sign. Then I don't understand. If it supports brace-initialisation for non-PODs, why is it complaining about QBasicAtomicInt? I took the preprocessor output of one of the moc_*.cpp files and find that it comes down to something like this: struct A { int a; A(int value) : a(value) {} }; struct S { A a; }; S s { { -1 } }; // error A a { -1 }; // OK A aa( -1 ); // OK Error with Clang 3.1: error: initialization of non-aggregate type 'A' with an initializer list S s { { -1 } }; ^~ It seems the added constructor is confusing Clang. The same code compiles fine with GCC 4.7. In Qt 5's case. A is QBasicAtomicInt and S is QtPrivate::RefCount. If that makes sense. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Container refactor update
On 6/20/12 6:20 PM, André Pönitz wrote: On Tue, Jun 19, 2012 at 09:55:28PM -0400, Stephen Chu wrote: Just a reminder that these changes are causing failure to build debug dumper in Creator. https://bugreports.qt-project.org/browse/QTCREATORBUG-7558 I think this is fixed in current master branch. Until further notice, or until Qt 5.0 is out, you will have to have a recent Qt Creator build if you want to have dumpers matching a current Qt 5.0 build. There have been changes to the Qt containers after the Qt Creator 2.5 release, and there are probably one or two more to come. I tried pretty hard to keep 2.5 as up-to-date as possible to the Qt 5 branch at the time of release, but one cannot expect to be able to predict details of not-yet-invented changes ;-} Andre' PS: A side note: I really appreciate the current work on the containers, and requiring a up-to-date Qt Creator to handle a bleeding edge version of Qt seems a reasonable price for the improvements. Of course, I also appreciate a friendly nudge _before_ someone touches containers, or QObject internals. Thanks. Is a completely new Creator required for it to work or just the files (dumper.cpp, etc) for building the dumper? Try as I might, I just cannot get Creator built in my system. If replacing the dumper source files is all it takes, I can do the surgery easily. :) Or will there be snapshots available? I see Windows and Linux ones but never Mac version at http://builds.qt-project.org/view/Qt%20Creator/ ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] buildsystem branches (about to be) integrated
On 6/19/12 8:31 AM, Oswald Buddenhagen wrote: moin, the buildsystem branch of qtbase is currently being integrated. this is ~120 commits worth of qmake project file fixes and cleanups. there are some changes to how modularization (in particular configure tests) is handled, and cross-building should be supported without hacks finally. the immediate impact: - lots of build scripts which employ various hacks will instantly break. don't panic and (mostly) just delete some code from them. use configure -xplatform spec -sysroot root make as you would intuitively expect. don't play tricks with funny qmake and make invocations. - the other modules will spit out lots of warnings now. *DON'T* do anything about them for now. i have patches prepared for all modules already. i will explicitly add the module owners to the reviews. *don't* stage anything yourself. once my patches are through, there will be still some warnings left. you'll be invited to fix them at this point. - some build configurations will work even worse than before until everything is integrated. the only variants which are expected to be safe are developer builds without -prefix and module-by-module builds with -prefix. catch me on IRC if something breaks for you and no obvious solution seems to help. but remember that not every breakage is due to this branch being integrated. ;) Is this buildsystem branch the one we get when we just clone qt5 clean? By that I mean if I go through the steps documented here: http://qt-project.org/wiki/Building-Qt-5-from-Git is that the same as this branch. The reason I ask is I just cloned qt5 from gitorious and saw a lot of updates. I am wonder if this will fix the broken build issue on Mac OS X. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Can't switch submodules to master and Mac build still broken
On 6/18/12 10:24 AM, shane.kea...@accenture.com wrote: You might be able to get the script working by changing the port in your ~/.ssh/config file Host codereview.qt-project.org Port 29418 User (your name) That makes ssh://codereview.qt-project.org/... expand to ssh://(your name)@codereview.qt-project.org:29418/... In case the script relies on this behaviour. (above configuration was in the gerrit setup wiki page) Thanks. But all I am trying to do is to get Qt 5 built in OS X. It's broken for over a week. This is just too time consuming to figure out all the tricks and secrets to do it. And we (general public and dumb developer-users) are not supposed to build off master branches anyway. The Qt 5 git repo is supposed to be composed of versions of sub-modules that works together, most of them not master. The fix is in qtbase master but never made it to the main Qt 5 mixture. For the time being, I will just go back to alpha-1. Thanks for the help. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Can't switch submodules to master and Mac build still broken
On 6/17/12 6:40 PM, Rohan McGovern wrote: Stephen Chu said: I still can't get Qt 5 build on OS X for the merged code (https://codereview.qt-project.org/#change,28604) hasn't showed up in Qt 5 git default yet. So I want to to try moving modules to master to get the fixes by the instruction here: http://qt-project.org/wiki/Building-Qt-5-from-Git#181b27e32ae791e987cb19fced190543 With qt5_tool method I got: Examining: qt3d url: git://gitorious.org/qt/qt3d.git ### [qt3d] /usr/bin/git fetch --all Fetching origin Fetching gerrit ssh: connect to host codereview.qt-project.org port 22: Connection refused This last message indicates something is wrong with the configuration. It should be attempting to connect to port 29418, not port 22. Maybe you can try with standard git commands instead of qt5_tool? I did as I mentioned in OP. It doesn't work either: Stephens-MacBook-Pro:qt3d stephenchu$ git checkout master origin/master error: pathspec 'origin/master' did not match any file(s) known to git. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build error in bluetooth module on Mac OS X 10.6
On 6/15/12 6:02 AM, shane.kea...@accenture.com wrote: Proposed real fix is here: https://codereview.qt-project.org/#change,28604 I see that the change has been merged. How long will it be before it can be pulled from git? I can see it in qtbase master branch but not yet in qt5 pull. These should be the same thing, have you tried 'git submodule update' ? I don't use the qt5.git repository, but that looks like the right command based on reading the git-submodule man page. Pulling qt5 from git doesn't use master branch in each module. It's stated here: http://qt-project.org/wiki/Building-Qt-5-from-Git#181b27e32ae791e987cb19fced190543 Right now the mixture doesn't have any of the fixes. I need to switch qtbase to master to have them but that causes other build errors. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build error in bluetooth module on Mac OS X 10.6
On 6/15/12 8:31 AM, Stephen Chu wrote: On 6/15/12 6:02 AM, shane.kea...@accenture.com wrote: Proposed real fix is here: https://codereview.qt-project.org/#change,28604 I see that the change has been merged. How long will it be before it can be pulled from git? I can see it in qtbase master branch but not yet in qt5 pull. These should be the same thing, have you tried 'git submodule update' ? I don't use the qt5.git repository, but that looks like the right command based on reading the git-submodule man page. Pulling qt5 from git doesn't use master branch in each module. It's stated here: http://qt-project.org/wiki/Building-Qt-5-from-Git#181b27e32ae791e987cb19fced190543 Right now the mixture doesn't have any of the fixes. I need to switch qtbase to master to have them but that causes other build errors. BTW. The snapshots here: http://releases.qt-project.org/qt5.0/beta-snapshots/ also don't have the fixes either. Since it's the snapshot of current git repo. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Can't switch submodules to master and Mac build still broken
I still can't get Qt 5 build on OS X for the merged code (https://codereview.qt-project.org/#change,28604) hasn't showed up in Qt 5 git default yet. So I want to to try moving modules to master to get the fixes by the instruction here: http://qt-project.org/wiki/Building-Qt-5-from-Git#181b27e32ae791e987cb19fced190543 With qt5_tool method I got: Examining: qt3d url: git://gitorious.org/qt/qt3d.git ### [qt3d] /usr/bin/git fetch --all Fetching origin Fetching gerrit ssh: connect to host codereview.qt-project.org port 22: Connection refused fatal: The remote end hung up unexpectedly error: Could not fetch gerrit fetch of qt3d failed at ./qtrepotools/bin/qt5_tool line 505. Using manual commands, I got: Stephens-MacBook-Pro:qt3d stephenchu$ git checkout master origin/master error: pathspec 'origin/master' did not match any file(s) known to git. I really don't know what to do to get it build on Mac now. It's really tiring trying all the things without any results. :( ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Can't switch submodules to master and Mac build still broken
On 6/15/12 1:25 PM, Thiago Macieira wrote: On sexta-feira, 15 de junho de 2012 13.11.59, Stephen Chu wrote: Stephens-MacBook-Pro:qt3d stephenchu$ git checkout master origin/master error: pathspec 'origin/master' did not match any file(s) known to git. What is your origin repository's URL? No idea. I don't know git well enough. It's part of a fresh git pull from the command: git clone git://gitorious.org/qt/qt5.git qt5 Basically I went through the steps according to: http://qt-project.org/wiki/Building-Qt-5-from-Git 1. Pulled Qt 5 from gitorious 2. Inited repository 3. Ran qt5_tool -p to move to master 4. That didn't work so I tried manually check out. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build error in bluetooth module on Mac OS X 10.6
On 6/13/12 8:38 AM, Sean Harmer wrote: On Wednesday 13 June 2012 11:01:39 Nils Jeisecke wrote: Hi, cherry picking https://codereview.qt-project.org/#change,28557 helped to complete the build. Proposed real fix is here: https://codereview.qt-project.org/#change,28604 I see that the change has been merged. How long will it be before it can be pulled from git? I can see it in qtbase master branch but not yet in qt5 pull. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] C++11 in Qt5
On 6/13/12 2:49 PM, bradley.hug...@nokia.com wrote: This is a new error that we also stumbled over today. Essentially, we can't enable C++11 language support in the compiler while the C++ library doesn't provide C++11 headers or features. It's all or nothing. There are some other errors involving constexpr in some Qt headers too: https://bugreports.qt-project.org/browse/QTBUG-25817 To deal with this, we'll have to introduce a way to switch the C++ runtime when building for Mac OS X. The best option to do this is with a new mkspec. I have a commit that needed testing (i.e. I started the compile before I left work today). I'll upload the commits to Gerrit tomorrow. So basically once C++11 features are enabled, there's no way to deploy the built app to OS X 10.6 since there's no libc++ there? Also we will have to build Qt itself with libc++ linkage since we do want the resulting app to link against two different C++ runtime libraries. Right? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] C++11 in Qt5
On 6/13/12 2:59 PM, Stephen Chu wrote: On 6/13/12 2:49 PM, bradley.hug...@nokia.com wrote: This is a new error that we also stumbled over today. Essentially, we can't enable C++11 language support in the compiler while the C++ library doesn't provide C++11 headers or features. It's all or nothing. There are some other errors involving constexpr in some Qt headers too: https://bugreports.qt-project.org/browse/QTBUG-25817 I mean when using libc++ with clang 3.1 To deal with this, we'll have to introduce a way to switch the C++ runtime when building for Mac OS X. The best option to do this is with a new mkspec. I have a commit that needed testing (i.e. I started the compile before I left work today). I'll upload the commits to Gerrit tomorrow. So basically once C++11 features are enabled, there's no way to deploy the built app to OS X 10.6 since there's no libc++ there? Also we will have to build Qt itself with libc++ linkage since we do want the resulting app to link against two different C++ runtime libraries. Right? I mean we *don't* want to link against two different C++ runtime. Gee. Really need my afternoon coffee now... ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Build error in bluetooth module on Mac OS X 10.6
I have the same problem building from the latest git on 10.7. It seems that QtV8 fails to generate a release build of the framework? I find only QtV8_debug in the resulting framework folder. The build script is having problem detecting error of sub-module. It always continues building (with errors) and reports build done at the end. On 6/11/12 12:19 PM, Nils Jeisecke wrote: Hi! I'm trying to build Qt5 on the Mac following the wiki page instructions. It fails when compiling the bluetooth qml module: g++ -headerpad_max_install_names -mmacosx-version-min=10.6 -single_module -dynamiclib -o libdeclarative_bluetooth_debug.dylib .obj/debug-shared/plugin.o .obj/debug-shared/qdeclarativebluetoothservice.o .obj/debug-shared/qdeclarativebluetoothsocket.o .obj/debug-shared/qdeclarativebluetoothdiscoverymodel.o .obj/debug-shared/qdeclarativebluetoothimageprovider.o .obj/debug-shared/moc_qdeclarativebluetoothservice_p.o .obj/debug-shared/moc_qdeclarativebluetoothsocket_p.o .obj/debug-shared/moc_qdeclarativebluetoothdiscoverymodel_p.o .obj/debug-shared/qrc_bluetooth.o -F/Users/njeiseck/projects/qt/qt5/qtbase/lib -L/Users/njeiseck/projects/qt/qt5/qtbase/lib -framework QtQuick -L/Users/njeiseck/projects/qt/qt5/qtbase/lib -F/Users/njeiseck/projects/qt/qt5/qtbase/lib -framework QtQml -framework QtNetwork -framework QtCore -framework QtV8 -framework QtGui -framework QtBluetooth -framework QtConcurrent -framework OpenGL -framework AGL ld: framework not found QtQuick collect2: ld returned 1 exit status make[4]: *** [../../../../qtbase/imports/QtBluetooth/libdeclarative_bluetooth_debug.dylib] Error 1 make[3]: *** [debug] Error 2 make[2]: *** [sub-bluetooth-make_default] Error 2 make[1]: *** [sub-imports-make_default-ordered] Error 2 make: *** [module-qtconnectivity-src-make_default-ordered] Error 2 I guess that QtQuick framework reference must come after the framework path. However I'm not yet familiar with the Qt 5 build system, so any hint where to fix that would be appreciated. Thanks! Nils ___ 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] FW: Alpha 2 this week or skip it
On 6/1/12 12:46 PM, Thiago Macieira wrote: On sábado, 2 de junho de 2012 00.18.48, techabc wrote: btw, Is there would win32-clang appears? That sentence did not make sense. I'm assuming you meant to ask is there a chance a win32-clang option would appear? Yes, there's a chance. Contribute the mkspec that works for you and we'll add it. This is kind of OT but is there even a working Win32 clang compiler? Last time I hear they are still have problem with MFC and other MS headers. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiler errors with clang 3.1
On 5/18/12 4:56 PM, Stephen Chu wrote: https://bugreports.qt-project.org/browse/QTBUG-25817 I tried both MacPort clang 3.1 and Apple's so-called LLVM 4.0 to build Qt and create apps with C++11 turned on. Both failed with constexpr errors. On the other hand, compiling using gcc 4.7 is successful. I am not sure if gcc is more lex on this or Q_DECL_CONSTEXPR macro is not defined. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development BTW. Apple LLVM 4 (clang 3.1) is from Xcode 4.4 DP5. Once Apple ships Xcode 4.4, it will become the default compiler in both 10.8 and 10.7. Just a heads up. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiler errors with clang 3.1
On 5/21/12 4:28 PM, Thiago Macieira wrote: On sexta-feira, 18 de maio de 2012 16.56.09, Stephen Chu wrote: On the other hand, compiling using gcc 4.7 is successful. I am not sure if gcc is more lex on this or Q_DECL_CONSTEXPR macro is not defined. GCC seems to be more lax. I recommend providing us with fixes to make Qt compile under that compiler. It looks to me that GCC is wrong on allowing it. I don't really know how to fix it but I will try. Does anyone know the purpose of declaring those functions constexpr? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiler errors with clang 3.1
On 5/21/12 5:22 PM, Thiago Macieira wrote: On segunda-feira, 21 de maio de 2012 17.07.51, Stephen Chu wrote: On 5/21/12 4:28 PM, Thiago Macieira wrote: On sexta-feira, 18 de maio de 2012 16.56.09, Stephen Chu wrote: On the other hand, compiling using gcc 4.7 is successful. I am not sure if gcc is more lex on this or Q_DECL_CONSTEXPR macro is not defined. GCC seems to be more lax. I recommend providing us with fixes to make Qt compile under that compiler. It looks to me that GCC is wrong on allowing it. I don't really know how to fix it but I will try. Does anyone know the purpose of declaring those functions constexpr? In most cases, the idea was to make the type be static-initialisable. I can't find any non-private use of this constructor: Q_DECL_CONSTEXPR inline QByteArray(QByteArrayDataPtr dd) : d(reinterpret_castData *(dd.ptr)) { } And I don't think it can ever be made a constexpr. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Compiler errors with clang 3.1
https://bugreports.qt-project.org/browse/QTBUG-25817 I tried both MacPort clang 3.1 and Apple's so-called LLVM 4.0 to build Qt and create apps with C++11 turned on. Both failed with constexpr errors. On the other hand, compiling using gcc 4.7 is successful. I am not sure if gcc is more lex on this or Q_DECL_CONSTEXPR macro is not defined. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] The place of QML
On 5/12/12 5:01 PM, Thiago Macieira wrote: On sábado, 12 de maio de 2012 22.28.40, Thiago Macieira wrote: Developers like you might be the numerical majority, but when it comes to number of products developed and shipped to customers, I'm pretty sure that no one will come close to next billion. Correcting myself. There is one who has already: http://www.videolan.org/vlc/stats/downloads.html Are they switching over to QML? jk... :) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development