This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Using kdevelop on Macbook pro retina

Tags: None
(comma "," separated)
athrunarthur
Registered Member
Posts
9
Karma
0
Hi,

I'm trying to use kdevelop on my macbook pro without starting a linux virtual machine. I found some solutions and tried them, but seems cannot work perfectly still.

Here are some solutions I've tried, and also the problems,
1. install kdevelop with brew ---- failed
https://github.com/adymo/homebrew-kde
I got error message like this when I type "brew install kdevelop",
Error: You must `brew link xz qt d-bus' before kdevelop can be installed
Warning: It appears you have MacPorts or Fink installed.
Software installed with other package managers causes known problems for
Homebrew. If a formula fails to build, uninstall MacPorts/Fink and try again.

After checking this message, I typed "brew link xz qt dbus", then I got
Linking /usr/local/Cellar/xz/5.0.5...
Error: Could not symlink lib/pkgconfig/liblzma.pc
/usr/local/lib/pkgconfig is not writable.


2. install kdevelop with macports, https://techbase.kde.org/Getting_Starte ... X/MacPorts
Basically, this method works, and I can start kdevelop. But the problem is my Mac is retina display, so the text and icons in kdevelop looks quite fuzzy.

3. Compile kdevelop from src code
After trying macport and homebrew, I decided to compile kdevelop from source code. The compiling seems successful. However, I failed to start it with this error message
WARNING: deleting stale lockfile /Users/xxx/Library/Preferences/KDE/share/apps/kdevelop/sessions/{e749111a-e737-4141-9cef-a14d38dda70d}/lock
kdevelop(63641)/kdevplatform (language) {anonymous}::shouldClear: version-hint not found, seems to be an old version
kdevelop(63641)/kdevplatform (language) KDevelop::ItemRepositoryRegistryPrivate::open: "The data-repository at /Users/xxx/.cache/kdevduchain/KDevelop- {e749111a-e737-4141-9cef-a14d38dda70d} has to be cleared."
Killed: 9

Also I wonder it's still fuzzy because of retina display even if I can start it.


So is there anyone are using kdevelop on Macbook pro retina? Any suggestions are appreciated.

Thanks
Athrun
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
For the 3rd failure, please try deleting the contents of /Users/xxx/.cache/kdevduchain/ using Finder, then trying to start KDevelop again.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:For the 3rd failure, please try deleting the contents of /Users/xxx/.cache/kdevduchain/ using Finder, then trying to start KDevelop again.


Thanks for your kind reply. I tried as you suggested, and it doesn't work, :(. I get this error now.

WARNING: deleting stale lockfile /Users/xxx/Library/Preferences/KDE/share/apps/kdevelop/sessions/{e749111a-e737-4141-9cef-a14d38dda70d}/lock
Killed: 9


Any ideas now?

Thanks
Athrun
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Please try removing the content of /Users/xxx/Library/Preferences/KDE/share/apps/kdevelop as well.
If this doesn't work, it may be necessary to start KDevelop under a debugger - are you familiar with this process under OS X?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:Please try removing the content of /Users/xxx/Library/Preferences/KDE/share/apps/kdevelop as well.
If this doesn't work, it may be necessary to start KDevelop under a debugger - are you familiar with this process under OS X?


Nope, still doesn't work. Seems need to start kdevelop under a debugger as you suggested. Unfortunately, I don't know how to do it. Can you please explain it to me?

Thanks
Athrun
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Please use LLDB to generate a backtrace. As i'm unfamiliar with Mac OS X, i'd suggest referencing Apple's documentation at https://developer.apple.com/support/tec ... debugging/


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:Please use LLDB to generate a backtrace. As i'm unfamiliar with Mac OS X, i'd suggest referencing Apple's documentation at https://developer.apple.com/support/tec ... debugging/


If you mean using LLDB to check why it's stopped, I tried. And here is the information

Process 84396 launched: './kdevelop' (x86_64)
WARNING: deleting stale lockfile /Users/xuepengfan/Library/Preferences/KDE/share/apps/kdevelop/sessions/{e749111a-e737-4141-9cef-a14d38dda70d}/lock
Process 84396 stopped
* thread #1: tid = 0x7b194c, 0x0000000114e274c2 libkdevplatforminterfaces.9.dylib`KDevelop::IPlugin::IPlugin(this=0x000000010cf9f500, instance=<unavailable>, parent=<unavailable>) + 338 at iplugin.cpp:108, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
frame #0: 0x0000000114e274c2 libkdevplatforminterfaces.9.dylib`KDevelop::IPlugin::IPlugin(this=0x000000010cf9f500, instance=<unavailable>, parent=<unavailable>) + 338 at iplugin.cpp:108
105 this, SLOT(_k_guiClientAdded(KXMLGUIClient*)));
106 }
107
-> 108 connect(ICore::self()->projectController(),
109 SIGNAL(projectOpened(KDevelop::IProject*)),
110 this, SLOT(_k_updateState()));


Also, the call stack:
* thread #1: tid = 0x7b194c, 0x0000000114e274c2 libkdevplatforminterfaces.9.dylib`KDevelop::IPlugin::IPlugin(this=0x000000010cf9f500, instance=<unavailable>, parent=<unavailable>) + 338 at iplugin.cpp:108, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
* frame #0: 0x0000000114e274c2 libkdevplatforminterfaces.9.dylib`KDevelop::IPlugin::IPlugin(this=0x000000010cf9f500, instance=<unavailable>, parent=<unavailable>) + 338 at iplugin.cpp:108
frame #1: 0x000000011278b5a6 kdevclassbrowser.so`ClassBrowserPlugin::ClassBrowserPlugin(this=0x000000010cf9f500, parent=0x0000000105f0ece0, (null)=<unavailable>) + 70 at classbrowserplugin.cpp:87
frame #2: 0x000000011278c108 kdevclassbrowser.so`QObject* KPluginFactory::createInstance<ClassBrowserPlugin, QObject>(parentWidget=<unavailable>, parent=<unavailable>, args=0x00007fff5fbff390) + 56 at kpluginfactory.h:477
frame #3: 0x000000010020721f libkdecore.5.dylib`KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) + 1039
frame #4: 0x000000010044f06d libkdevplatformshell.9.dylib`KDevelop::PluginController::loadPluginInternal(QString const&) + 80 at kpluginfactory.h:507
frame #5: 0x000000010044f01d libkdevplatformshell.9.dylib`KDevelop::PluginController::loadPluginInternal(this=0x0000000105f46a50, pluginId=0x00007fff5fbff530) + 4269
frame #6: 0x0000000100450bf4 libkdevplatformshell.9.dylib`KDevelop::PluginController::initialize(this=0x0000000105f46a50) + 2532 at plugincontroller.cpp:356
frame #7: 0x0000000100457047 libkdevplatformshell.9.dylib`KDevelop::CorePrivate::initialize(this=0x0000000108300090, mode=<unavailable>, session=<unavailable>) + 1527 at core.cpp:244
frame #8: 0x0000000100458679 libkdevplatformshell.9.dylib`KDevelop::Core::initialize(splash=0x0000000108260270, mode=Default, session=0x00007fff5fbff840) + 137 at core.cpp:331
frame #9: 0x0000000100012afb kdevelop`main(argc=1606416448, argv=<unavailable>) + 15691 at main.cpp:467

Seems like cannot connect signal-slot? Although I'm kind of familiar with C++, totally have no experience about QT or KDE.

Thanks for you help.
-Athrun

Last edited by athrunarthur on Sat Aug 16, 2014 9:14 am, edited 2 times in total.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Can you please generate a complete backtrace - that appears to only be the first line.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:Can you please generate a complete backtrace - that appears to only be the first line.

you mean the call stack?

* thread #1: tid = 0x7b194c, 0x0000000114e274c2 libkdevplatforminterfaces.9.dylib`KDevelop::IPlugin::IPlugin(this=0x000000010cf9f500, instance=<unavailable>, parent=<unavailable>) + 338 at iplugin.cpp:108, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
* frame #0: 0x0000000114e274c2 libkdevplatforminterfaces.9.dylib`KDevelop::IPlugin::IPlugin(this=0x000000010cf9f500, instance=<unavailable>, parent=<unavailable>) + 338 at iplugin.cpp:108
frame #1: 0x000000011278b5a6 kdevclassbrowser.so`ClassBrowserPlugin::ClassBrowserPlugin(this=0x000000010cf9f500, parent=0x0000000105f0ece0, (null)=<unavailable>) + 70 at classbrowserplugin.cpp:87
frame #2: 0x000000011278c108 kdevclassbrowser.so`QObject* KPluginFactory::createInstance<ClassBrowserPlugin, QObject>(parentWidget=<unavailable>, parent=<unavailable>, args=0x00007fff5fbff390) + 56 at kpluginfactory.h:477
frame #3: 0x000000010020721f libkdecore.5.dylib`KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) + 1039
frame #4: 0x000000010044f06d libkdevplatformshell.9.dylib`KDevelop::PluginController::loadPluginInternal(QString const&) + 80 at kpluginfactory.h:507
frame #5: 0x000000010044f01d libkdevplatformshell.9.dylib`KDevelop::PluginController::loadPluginInternal(this=0x0000000105f46a50, pluginId=0x00007fff5fbff530) + 4269
frame #6: 0x0000000100450bf4 libkdevplatformshell.9.dylib`KDevelop::PluginController::initialize(this=0x0000000105f46a50) + 2532 at plugincontroller.cpp:356
frame #7: 0x0000000100457047 libkdevplatformshell.9.dylib`KDevelop::CorePrivate::initialize(this=0x0000000108300090, mode=<unavailable>, session=<unavailable>) + 1527 at core.cpp:244
frame #8: 0x0000000100458679 libkdevplatformshell.9.dylib`KDevelop::Core::initialize(splash=0x0000000108260270, mode=Default, session=0x00007fff5fbff840) + 137 at core.cpp:331
frame #9: 0x0000000100012afb kdevelop`main(argc=1606416448, argv=<unavailable>) + 15691 at main.cpp:467
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
In which directory did you install KDevelop? It looks like it is failing to load the ui.rc files needed by the plugins.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:In which directory did you install KDevelop? It looks like it is failing to load the ui.rc files needed by the plugins.


I installed Kdevelop into my own directory. However, I do notice that there are some differences compared to Linux.
The main difference is no .rc files in the installed directory.
Here is the directory tree of my install directory.
./
├── bin
├── include
│   ├── kdevelop
│   │   ├── custom-definesandincludes
│   │   └── make
│   └── kdevplatform
│   ├── debugger
│   │   ├── breakpoint
│   │   ├── framestack
│   │   ├── interfaces
│   │   ├── util
│   │   └── variable
│   ├── documentation
│   ├── execute
│   ├── executescript
│   ├── interfaces
│   ├── language
│   │   ├── assistant
│   │   ├── backgroundparser
│   │   ├── checks
│   │   ├── codecompletion
│   │   ├── codegen
│   │   ├── duchain
│   │   │   ├── builders
│   │   │   ├── navigation
│   │   │   ├── repositories
│   │   │   └── types
│   │   ├── editor
│   │   ├── highlighting
│   │   ├── interfaces
│   │   └── util
│   ├── openwith
│   ├── outputview
│   ├── project
│   │   └── interfaces
│   ├── shell
│   ├── sublime
│   ├── tests
│   │   └── json
│   ├── util
│   └── vcs
│   ├── dvcs
│   │   └── ui
│   ├── interfaces
│   ├── models
│   └── widgets
├── lib
│   ├── cmake
│   │   └── kdevplatform
│   └── kde4
│   ├── imports
│   │   └── org
│   │   └── kde
│   │   └── kdevplatform
│   └── plugins
│   └── grantlee
│   └── 0.3
└── share
├── applications
│   └── kde4
├── apps
│   ├── cmake
│   │   └── modules
│   ├── kdevappwizard
│   │   └── templates
│   ├── kdevclassbrowser
│   ├── kdevcodegen
│   │   ├── licenses
│   │   └── templates
│   ├── kdevcodeutils
│   │   └── templates
│   ├── kdevcontextbrowser
│   ├── kdevcppsupport
│   ├── kdevcustommakemanager
│   ├── kdevcvs
│   ├── kdevdebugger
│   ├── kdevdocumentswitcher
│   ├── kdevdocumentview
│   ├── kdevelop
│   │   ├── icons
│   │   │   └── hicolor
│   │   │   ├── 16x16
│   │   │   │   └── actions
│   │   │   ├── 22x22
│   │   │   │   └── actions
│   │   │   └── 32x32
│   │   │   └── actions
│   │   └── pics
│   ├── kdevexternalscript
│   ├── kdevfilemanager
│   ├── kdevfiletemplates
│   │   └── templates
│   ├── kdevgrepview
│   ├── kdevmanpage
│   ├── kdevpatchreview
│   ├── kdevproblemreporter
│   ├── kdevprojectmanagerview
│   ├── kdevquickopen
│   ├── kdevsession
│   ├── kdevsnippet
│   ├── kdevsourceformatter
│   ├── kdevstandardoutputview
│   ├── kdevtestview
│   └── plasma
│   ├── plasmoids
│   │   ├── kdevelopsessions
│   │   │   └── contents
│   │   │   └── ui
│   │   └── org.kdevelop.branches
│   │   └── contents
│   │   └── qml
│   └── services
├── config
├── doc
│   └── HTML
│   └── en
│   └── kdevelop
├── icons
│   └── hicolor
│   ├── 128x128
│   │   └── apps
│   ├── 16x16
│   │   └── apps
│   ├── 22x22
│   │   └── actions
│   ├── 32x32
│   │   └── apps
│   ├── 48x48
│   │   └── apps
│   └── 64x64
│   └── apps
├── kde4
│   ├── services
│   └── servicetypes
└── mime
├── packages
└── text


Also, I find that everything can be found in the build directory, the location is
kdevelop/build/app/kdevelop.app/Contents/MacOs
Of course I cannot run kdevelop directly under the build directory, But it seems the installation didn't try to put all things into install dir, right?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The missing ui.rc files in this case are the cause of the crash - they're rather crucial to the operation of KDevelop.
Are the ui.rc files contained within the kdevelop.app bundle?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:The missing ui.rc files in this case are the cause of the crash - they're rather crucial to the operation of KDevelop.
Are the ui.rc files contained within the kdevelop.app bundle?


Do you mean the kdevelopui.rc ? Yeah, I can find it in both the app bundle folder and the installation folder. In case I was wrong with the file name, I'd like to list all rc files in the app bundle folder:

./app/kdevelop.app/Contents/MacOS/kdevappwizard/kdevappwizard.rc
./app/kdevelop.app/Contents/MacOS/kdevclassbrowser/kdevclassbrowser.rc
./app/kdevelop.app/Contents/MacOS/kdevcodeutils/kdevcodeutils.rc
./app/kdevelop.app/Contents/MacOS/kdevcontextbrowser/kdevcontextbrowser.rc
./app/kdevelop.app/Contents/MacOS/kdevcppsupport/kdevcppsupport.rc
./app/kdevelop.app/Contents/MacOS/kdevcustommakemanager/kdevcustommakemanager.rc
./app/kdevelop.app/Contents/MacOS/kdevcvs/kdevcvs.rc
./app/kdevelop.app/Contents/MacOS/kdevdebugger/kdevdebuggershellui.rc
./app/kdevelop.app/Contents/MacOS/kdevdocumentswitcher/kdevdocumentswitcher.rc
./app/kdevelop.app/Contents/MacOS/kdevdocumentview/kdevdocumentview.rc
./app/kdevelop.app/Contents/MacOS/kdevexternalscript/kdevexternalscript.rc
./app/kdevelop.app/Contents/MacOS/kdevfilemanager/kdevfilemanager.rc
./app/kdevelop.app/Contents/MacOS/kdevfiletemplates/kdevfiletemplates.rc
./app/kdevelop.app/Contents/MacOS/kdevgrepview/kdevgrepview.rc
./app/kdevelop.app/Contents/MacOS/kdevpatchreview/kdevpatchreview.rc
./app/kdevelop.app/Contents/MacOS/kdevproblemreporter/kdevproblemreporter.rc
./app/kdevelop.app/Contents/MacOS/kdevprojectmanagerview/kdevprojectmanagerview.rc
./app/kdevelop.app/Contents/MacOS/kdevquickopen/kdevquickopen.rc
./app/kdevelop.app/Contents/MacOS/kdevsession/kdevsessionui.rc
./app/kdevelop.app/Contents/MacOS/kdevsnippet/kdevsnippet.rc
./app/kdevelop.app/Contents/MacOS/kdevsourceformatter/kdevsourceformatter.rc
./app/kdevelop.app/Contents/MacOS/kdevstandardoutputview/kdevstandardoutputview.rc
./app/kdevelop.app/Contents/MacOS/kdevtestview/kdevtestview.rc


And also the rc files in the installation folder (Actually the are same with the files in the bundle folder)
./share/apps/kdevappwizard/kdevappwizard.rc
./share/apps/kdevclassbrowser/kdevclassbrowser.rc
./share/apps/kdevcodeutils/kdevcodeutils.rc
./share/apps/kdevcontextbrowser/kdevcontextbrowser.rc
./share/apps/kdevcppsupport/kdevcppsupport.rc
./share/apps/kdevcustommakemanager/kdevcustommakemanager.rc
./share/apps/kdevcvs/kdevcvs.rc
./share/apps/kdevdebugger/kdevdebuggershellui.rc
./share/apps/kdevdocumentswitcher/kdevdocumentswitcher.rc
./share/apps/kdevdocumentview/kdevdocumentview.rc
./share/apps/kdevelop/katepartui.rc
./share/apps/kdevelop/kdevelopui.rc
./share/apps/kdevexternalscript/kdevexternalscript.rc
./share/apps/kdevfilemanager/kdevfilemanager.rc
./share/apps/kdevfiletemplates/kdevfiletemplates.rc
./share/apps/kdevgrepview/kdevgrepview.rc
./share/apps/kdevpatchreview/kdevpatchreview.rc
./share/apps/kdevproblemreporter/kdevproblemreporter.rc
./share/apps/kdevprojectmanagerview/kdevprojectmanagerview.rc
./share/apps/kdevquickopen/kdevquickopen.rc
./share/apps/kdevsession/kdevsessionui.rc
./share/apps/kdevsnippet/kdevsnippet.rc
./share/apps/kdevsourceformatter/kdevsourceformatter.rc
./share/apps/kdevstandardoutputview/kdevstandardoutputview.rc
./share/apps/kdevtestview/kdevtestview.rc


Any ideas?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Can you please post the content of the "share/apps/kdevclassbrowser/kdevclassbrowser.rc" file?
Just to confirm - the share/apps/kdevclassbrowser/kdevclassbrowser.rc file does exist within the installation directory you have used for KDevelop (and which in turn is either the same directory kdelibs is installed in, or is specified in KDEDIRS)?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
athrunarthur
Registered Member
Posts
9
Karma
0
bcooksley wrote:Can you please post the content of the "share/apps/kdevclassbrowser/kdevclassbrowser.rc" file?
Just to confirm - the share/apps/kdevclassbrowser/kdevclassbrowser.rc file does exist within the installation directory you have used for KDevelop (and which in turn is either the same directory kdelibs is installed in, or is specified in KDEDIRS)?


Here is the content in "share/apps/kdevclassbrowser/kdevclassbrowser.rc".

<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<kpartgui name="KDevClassBrowser" version="1">
</kpartgui>


About the KDEDIRS, I installed kdevelop into $HOME/kdevelop4, and my setting in .bash_profile is like this,
export KDEDIRS=$KDEDIRS:$HOME/kdevelop4:$HOME/Library/Preferences/KDE:/usr/local/kde4
export PATH=/usr/local/kde4/bin:$PATH
export DYLD_LIBRARY_PATH=/usr/local/kde4/lib:$DYLD_LIBRARY_PATH
launchctl setenv DYLD_LIBRARY_PATH /usr/local/kde4/lib:$DYLD_LIBRARY_PATH
export XDG_DATA_HOME=$HOME/Library/Preferences/KDE/share
export XDG_DATA_DIRS=/usr/local/kde4/share:/usr/local/share:/usr/share:$HOME/kdevelop4/share


Is there anything wrong?


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]