KDevelop 4.2.3 on Mac Lion

[Sven Brauch]

Hi,

about the background parser: This is the whole point of kdevelop,
switching it off turns kdevelop into an ordinary text editor.
It is normal for the parser to consume 100% CPU while it's working.
However, this load should go away after a few minutes (see progressbar
in lower right corner).

Bye,
Sven

2011/7/22 Patrice Kouame <patrice.kouame at gmail.com>:
> Hi  -
> I compiled the latest distribution on Mac 10.6.7 successfully.  It is
> however prone to crashing.  A few questions:
> 1 - I switched off debug for all kdevelop and kdevplatform modules in
> kdebugdialog but am still getting a zillion of these messages in my system
> log:
> 7/22/11 9:28:39.689 AM [0x0-0xd90d9].kdevelop: select: Invalid argument
> 2 - Out of the box it had the background parsing option ON which was
> consuming over 100% cpu even though I had just had one project (kdevelop)
> open at the time. Turning that option off did the trick, but the question
> still remains: does the indexing/parsing normally consume so much?
> 3 - What are the proper settings for XDG_DATA_DIRS and XDG_DATA_HOME. I
> followed the instructions on the build page to the letter, but sycoca4 still
> complains about missing mime types. Is /usr/local good enough or should it
> be /usr/local/share? The specification
>  http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html  recommends
> the respective share directories, but the docs
> at http://techbase.kde.org/KDevelop4/HowToCompile don't.  Also does
> DATA_HOME matter?
> 4- The application takes quite a long time to quit.
> 5- Deleting the last session quits the application. Here is the full log.
>  Is this normal?
> 7/22/11 10:43:45.794 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChain::finalCleanup: cleaned 39 B
> 7/22/11 10:43:45.794 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChain::finalCleanup: cleaned enough
> 7/22/11 10:43:45.794 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChain::finalCleanup: final cleanup ready
> 7/22/11 10:43:45.794 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChainPrivate::doMoreCleanup: starting cleanup
> 7/22/11 10:43:45.807 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChainPrivate::doMoreCleanup: seconds spent doing
> cleanup:  0 top-contexts still open: 0
> 7/22/11 10:43:45.807 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChainPrivate::doMoreCleanup: milliseconds spent doing
> cleanup with locked duchain:  14
> 7/22/11 10:43:45.813 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)
> Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed
> with sessions still alive
> 7/22/11 10:43:45.814 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kio (Slave)
> KIO::Slave::kill: killing slave pid 27675 ( "trash://" )
> 7/22/11 10:43:45.814 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kio (Slave)
> KIO::Slave::kill: killing slave pid 27704 ( "man://" )
> 7/22/11 10:43:45.814 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kio (Slave)
> KIO::Slave::kill: killing slave pid 27578 ( "file://" )
> 7/22/11 10:43:45.814 AM [0x0-0xea0ea].kdevelop: kdevelop(27576)/kdevplatform
> (language) KDevelop::DUChainPrivate::~DUChainPrivate: Destroying
> 7/22/11 10:43:45.866 AM [0x0-0xd20d2].org.kde.kdeinit4: klauncher(22594)/kio
> (KLauncher) KLauncher::slotGotOutput: kio_man(27704)/kio (kioslave)
> KIO::SlaveBase::dispatchLoop: slave was killed, returning
> 7/22/11 10:43:45.866 AM [0x0-0xd20d2].org.kde.kdeinit4: kio_man(27704)
> kdemain: Done
> 7/22/11 10:43:45.866 AM [0x0-0xd20d2].org.kde.kdeinit4: klauncher(22594)/kio
> (KLauncher) KLauncher::slotGotOutput: kio_file(27578)/kio (kioslave)
> KIO::SlaveBase::dispatchLoop: slave was killed, returning
> 7/22/11 10:43:45.866 AM [0x0-0xd20d2].org.kde.kdeinit4: kio_file(27578)
> kdemain: Done
> 7/22/11 10:43:45.866 AM [0x0-0xd20d2].org.kde.kdeinit4: klauncher(22594)/kio
> (KLauncher) KLauncher::slotGotOutput: kio_trash(27675)/kio (kioslave)
> KIO::SlaveBase::dispatchLoop: slave was killed, returning
> 7/22/11 10:43:45.871 AM [0x0-0xd20d2].org.kde.kdeinit4: klauncher(22594)/kio
> (KLauncher) KLauncher::slotFinished: process finished exitcode= 0
> exitStatus= 0
> 7/22/11 10:43:45.871 AM [0x0-0xd20d2].org.kde.kdeinit4: klauncher(22594)/kio
> (KLauncher) KLauncher::slotFinished: process finished exitcode= 0
> exitStatus= 0
> 7/22/11 10:43:45.873 AM [0x0-0xd20d2].org.kde.kdeinit4: klauncher(22594)/kio
> (KLauncher) KLauncher::slotFinished: process finished exitcode= 0
> exitStatus= 0
> 6- With a CMake based project up (again kdevelop itself) , the main menu
> preference button, invokes a Build window and runs cmake.  I kind of
> expected a preferences dialog of some kind.
> 7- Are the requirements on the build/compile page current.  I currently
> built a QT4 KDE4 CALLIGRA development environment from scratch with the
> latest masters from kde.org/projects.  Not sure if I need things like the
> kdeworkspace and samba or any other libraries but kderuntime, kdelibs,
> qt-kdev, automoc, attica, dbusmenuqt, etc… from the kde/mac pages.
> 8 - Last thing,  there is a blank row between the window frame and the main
> toolbar (the one with build, execute debug)  Am I missing a toolbar or is
> this just a bug on my platform.
> Thanks in advance, I know my platform is a little bleeding edge: Mac, Lion,
> Xcode 4.2 beta etc… but I would sure like to get this going and share my
> experience.
> Patrice
>
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>