3 Dec
2012
3 Dec
'12
10:20 p.m.
is your debugging setup properly? With gcc you need to specify to include
debugging symbols and such. It's possible that autoconf isn't setting the
debug flag
On 3 December 2012 16:57, John A. Sullivan III <
jsullivan(a)opensourcedevel.com> wrote:
On Fri, 2012-11-30 at 13:54 -0500, John A. Sullivan
III wrote:
Hello, all. I'm still doing occasional
battle with maintaining old Qt3
applications using KDevelop in Trinity 3.5.13.1 on Squeeze. When I
start KDevelop, I am asked to select a TQt3 directory which must have an
include directory containing tqt.h. On my system, tqt.h is
in /usr/include/tqt. However, the dialog does not like that path or any
parent along that path. What should this entry be?
This may be related to another problem. I am having problems running
the debugger in this qmake application. It often fails to find and
evaluate variables. Thanks - John
The debugging problem does not appear to be related. I am having the
same problem in ddd. Weird - when I used autoconf/automake, I had no
problem seeing file scope variables in the debugger. Now that I've
moved to qmake, I can see function scope variables but not file scope
even with 'filename.cpp'::variablename.
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting