[Bug 60008] building a new project

[Sphere]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=60008     




------- Additional Comments From sphere1952 at attbi.com  2003-06-18 22:14 -------
Subject: Re:  building a new project

John Birch wrote:

>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
>     
>http://bugs.kde.org/show_bug.cgi?id=60008     
>
>
>
>
>------- Additional Comments From jbb at kdevelop.org  2003-06-18 21:51 -------
>I've already changed the C++ App template to default to a debug version a 
>couple of weeks ago. The other projects are awaiting changes. Any patches that 
>does this would be applied immediately. 
> 
>What version of kdevelop are you using? I strongly recommend that you update to 
>the latest version using cvs. 
> 
>The walkthrough is a separate issue, although I'm not sure what you are really 
>asking for as it's a bit vague. Could you give an example of how you see this 
>working. 
> 
>Thanks, 
> 
>jbb
>

Thanks.

I've a gideon built from the cvs tree a few days ago and an older 
kdevelop from debian
testing.  I haven't been able to build a test in the older one, but I 
think that's
because the version of qt I found is too new. (I haven't really persued 
the matter
yet.)

I'm still trying to figure out how to get a somewhat maintainable cvs 
version
of kde together.  (It takes a long time to build...)  The first script I 
found eventually
gave me something to work with, but it didn't seem suitable for setting 
up a weekly
cron job to rebuild kde.  The second one shows more promise, but I'm still
working my way though it -- and some of the side issues.

At least the cvs gideon built something, but I've still got lib path 
issues (I think).
Some of my wishes are prompted by the fact that I can't wander through 
the code
and find out exactly what it is trying to load.

As far as "walk through" is concerned.  I want to be able to put a piece 
of code I'm
new to into the debugger and "walk though" the source code as it's 
running, so I
usually start out with a breakpoint at the main() entry point and step 
into interesting
constructors and the like.  What with events happening and all you 
generally have
to keep moving your breakpoints deeper into the code.  Of course, in 
order to be
able to do this you can't have the debugger deciding to thow up its' 
hands in failure
when you want to enter the qt lib (or such).