[Qt-interest] MSVC 2010 ready for Qt yet?

[Malyushytsky, Alex]

>> What exactly is the advantage in debugging when building Qt from source?

Even if you are not going to fix/find problems in Qt itself,
you often can find what is wrong with your code by stepping inside Qt functions.
This is only possible when you build Qt yourself (not counting reading assembly as a fun).

Alex


-----Original Message-----
From: qt-interest-bounces+alex=wai.com at qt.nokia.com [mailto:qt-interest-bounces+alex=wai.com at qt.nokia.com] On Behalf Of Benjamin
Sent: Friday, April 29, 2011 2:18 PM
To: qt-interest at qt.nokia.com
Subject: Re: [Qt-interest] MSVC 2010 ready for Qt yet?

Am 29.04.2011 19:32, schrieb slayer81 at gmx.de:
> So far I used the built binaries from the website.
> What exactly is the advantage in debugging when building Qt from source?
>
> Paule
>
> Am 29.04.2011 09:27:49, schrieb "Malyushytsky, Alex"<alex at wai.com>:
>

I'm not sure if there are differences, when debugging your own code, but
if you want to get information about the qt-methods and their behavior,
a self-compiled qt can be nice. You can instruct the compiler to not
omit frame-pointers, to add special debugging information for your
desired debugger (on linux you would want to add gdb-information with
the gcc; on windows I'm not sure, 'cause I don't use it :D) and you can
prevent strip-operations after the linking. With that, your lib will be
larger and maybe a little slower, but debugging will be much more
comfortable, because you don't have to read assembly ;)

best regards,
- Ben
_______________________________________________
Qt-interest mailing list
Qt-interest at qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-interest


---------------------------------------------------------------------------------------------------
Weidlinger Associates, Inc. made the following annotations.

“This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you.”

“Please consider our environment before printing this email.”