Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Stephen Kelly
On Thursday, September 13, 2012 07:33:52 Till Oliver Knoll wrote: Well, that's /exactly/ my point ;) By doing module includes I instantly realise at the earliest possible stage, at typing time (as opposed to compile- or link time), that Oops! That comes from QtWidgets! That shouldn't be here

Re: [Interest] Problem with qmake in qt5-beta on osx creating a static library

2012-09-13 Thread Thiago Macieira
On quarta-feira, 12 de setembro de 2012 17.49.19, Sid Deb wrote: Hi, I'm porting a graphics app from qt4.6 to qt5.0.beta1 and I've run into a situation where qmake refuses to name my output library correctly. I'm working on OSX 10.6.8. Here are the relevant items from the .pro file: CONFIG

Re: [Interest] [Development] QtDus Problem

2012-09-13 Thread Thiago Macieira
On quarta-feira, 12 de setembro de 2012 20.40.28, Sandro Andrade wrote: when i execute Quit() from d-feet, my RootAdapter Quit() funciton gets called, but i get this error: Warning: QMetaObject::invokeMethod: No such method QObject::Quit() Is the Quit() method a slot or was declared with

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Stephen Kelly
On Thursday, September 13, 2012 10:26:03 Thiago Macieira wrote: On quinta-feira, 13 de setembro de 2012 10.19.34, Stephen Kelly wrote: And if I would forget to say QT += widgets in model.pro, I'd simply get a linker error. Only if you attempt to use something from the header which

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Lincoln Ramsay
On 13/09/12 6:57 AM, Stephen Kelly wrote: Your build tools don't tell you that there is a problem. It compiles just fine (for you), even though the include should not be there. If you instead include QAction, your compiler will not find that header and you will immediately know you made a

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Till Oliver Knoll
Am 13.09.2012 um 10:19 schrieb Stephen Kelly stephen.ke...@kdab.com: ... flag -Wl,--no-undefined you won't get the error when you build a static library, but only when you link the target that uses that static library. Mysterious. Okay, I get your point there: however I still don't

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Stephen Chu
Well. This thread is getting a bit OT. Let me bring it back a little. :) My experience with Qt 5 with Mac is generally good. The only major issues for me right now is the window title focus bug and detached dock widget can't be reattached. I have to changed the app behavior to work around the

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Daniel Price
What are the issues with Apples version of Clang? The biggest problem I have with Qt + clang on the mac is the dismal debugging. I can't get LLDB to work with Creator and Apple's ancient GDB is worse than useless. -Original Message- From:

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Stephen Chu
On 9/13/12 10:41 AM, Daniel Price wrote: What are the issues with Apples version of Clang? Apple's Clang has different versions than the official Clang release. For example, the one in Xcode 4.4.1 claims to be 4.0 while Clang 3.2 is not released yet. This caused some problem in compiler feature

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Sylvain Pointeau
What are the issues with Apples version of Clang? The biggest problem I have with Qt + clang on the mac is the dismal debugging. I can't get LLDB to work with Creator and Apple's ancient GDB is worse than useless. I am in the process of compiling Qt 5 with clang+libc++ to have the full

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Stephen Kelly
On Thursday, September 13, 2012 13:56:33 Till Oliver Knoll wrote: Am 13.09.2012 um 10:19 schrieb Stephen Kelly stephen.ke...@kdab.com: ... flag -Wl,--no-undefined you won't get the error when you build a static library, but only when you link the target that uses that static library.

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Stephen Chu
On 9/13/12 11:18 AM, Harri Pasanen wrote: Kind of off topic, but if your code runs also on linux, I find developing with synergy works well. http://synergy-foss.org/ It gives the illusion your mac and linux boxes are one machine. It really feels real, copy-paste, mouse moves seamlessly

[Interest] Completed: JIRA Maintenance September 13 - bugreports.qt-project.org

2012-09-13 Thread Matias Rand
JIRA / bugreports.qt-project.org is up and running again. Upgraded to 5.0.7. Regards -- Matias Rand Nokia ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] My experience porting to Qt5 (on OS X)

2012-09-13 Thread Till Oliver Knoll
2012/9/13 Stephen Kelly stephen.ke...@kdab.com: ... Anyway, my advice is: Don't use module includes. Yes, and we'll leave it at that ;) I think this academic discussion about ordering and forgetting to remove #includes went on long enough: I do see your points and agree with you on them.

Re: [Interest] Problem with qmake in qt5-beta on osx creating a static library

2012-09-13 Thread Sid Deb
It turns out I was still using the mkspecs from qt 4.6. Updating to the 5.0 ones fixed this problem. Sorry for the noise, and thanks for the info. Sid On Sep 13, 2012, at 1:29 AM, Thiago Macieira wrote: On quarta-feira, 12 de setembro de 2012 17.49.19, Sid Deb wrote: Hi, I'm porting a

[Interest] Access to Qt private headers

2012-09-13 Thread ganesh.sathyanarayanan
Hi, Sorry, this has been asked before here http://lists.qt.nokia.com/pipermail/qt-interest/2011-October/036291.html, but I did not find the actual solution of how to do it. Also I tried the options of: QT += v8-private QT_PRIVATE = v8 PRIVATE_HEADERS = v8.h in the pro file, but none of them