[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 140594] kdevelop fails to evaluate local variables
From:       kbugger <kbugger () piments ! com>
Date:       2007-01-26 0:54:45
Message-ID: 20070126005445.14500.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=140594         
kbugger piments com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From kbugger piments com  2007-01-26 01:54 -------
many thanks for you help in clearing this up. 

I knew gnome projects are a bit non std in the way they use autotools but when I saw \
GNOME had a specific entry in the import project list I thought this was taken into \
account.

I was however very pleasantly surprised how far I got importing and building the gimp \
, especially since it needed installing with a non std prefix so as not to collide \
with a release version.

It was necessary to set AUTOMAKE_CONFIGURE_ARGS before starting kdevelop in order for \
it to be picked up by autogen.sh run from "automake&friends".

After that I re-ran configure from kdev and was able to note the CFLAGS -O0 -g in \
effect. I built the project , installed , set a breakpoint and ran gimp in the \
debugger.

Now I see all the variables in full Technicolor and with Dolby surround sound! ;)

For me kdevelop has definately come of age. Thanks for an impressive tool and for \
your help in sorting out this last step.

I'm not sure if moving from 3.3.94 to 3.4.0 was a key factor but I'll mark this as \
fixed.

Many thanks.


[prev in list] [next in list] [prev in thread] [next in thread]