code completion problem && some generic questions

[Alexander Neundorf]

On Thursday 09 March 2006 01:05, Andreas Pakulat wrote:
> On 08.03.06 23:59:38, Bernd Schubert wrote:
> > since kdevelop-3.3.0 using the code completion has a problem. Everytime
> > it tries to do the code completion, kdevelop gets stuck somewhere in the
> > code completition functions.
>
> This problem is known and IIRC fixed in SVN. I'm not sure wether there
> was a bugs.kde.org entry, I can't seem to find it ATM. There was
> definetly some discussion about this last year (search the last half of
> the year, this list doesn't have that many entries).
>
> > I would like to improve my C++ knowledge and so would like to fix this
> > myself.
>
> If there was/is a bug report for this, the fix is there. Else its in one
> of the mails regarind that topic. I'll see if I can find something...
>
> > 1.) Even though I compiled with --debug=full gdb traces don't show any
> > line numbers. I'm usually programming in C and never had this problem
> > before. Anyone knows the reason?
>
> I normally compile with --disable-finale --enable-debug, not the =full
> option. IIRC there were some discussions on kde-core-devel regarding the
> (not?) usefulness of =full. Unfortunately I don't remember it too well
> (only cross read the posts there). It must have been some time this year
> if I'm not mistaken (maybe dec last year).
>
> > 2.) Even though compiled with --debug=full, -O2 is still used. Where can
> > I disable -O2 or set -O0. Is this related to Q1?
>
> I think so, I'm not totally sure but I think gcc turns off debug
> information if you tell him to optimize. This may be the cause of using
> debug=full...
>
> > kdevelop supports cmake builds, I wanted to try that. The
> > CMakeLists.txt:23 of kdevelop-3.3.1 requests a subdirectory bdb, but
> > since its not there the cmake build fails.
>
> I wasn't aware that kdevelop is buildable with cmake, I thought only
> autotools+make, or unsermake is possible...
>
> Aah, there it is, a Changelog entry from Alexander Neundorf saying
> something about partial support for cmake. bdb was the kdevelop-shipped
> berkley-db, which is used for the code completion database. However I
> think the kdevelop-maintained bdb-copy is removed not only from
> svn-version but also from 3.3. So I guess the cmake-support is somewhat
> unmaintained.


Yes, this was my first try at compiling some kde stuff with cmake.
It worked mostly but is neither finished nor maintained (currently).
I already removed them in some branch, but apparrently not in all branches. 

To make it short: do not try to compile kdevelop with cmake.

Bye
Alex
-- 
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org                - http://www.kde.org
      alex AT neundorf.net               - http://www.neundorf.net