Install on Mac OS
Tags:
None
Administrator 
|
It seems that it is waiting for another thread to finish accessing some shared data (+ 2906 QMutexPrivate::wait(int) (in QtCore) + 141 [0x105b24d61]), but that itself has hung.
Can you try and get a backtrace which covers all the threads? If there are no other threads, there could be a bug that means a mutex isn't being released before a thread exits.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
KDE Developer
|
Hm... This is a hang right inside the kde application code. Do other KDE gui apps work?
|
Registered Member
|
@ bcook - seems like all apps hang on the same QMutex. The last checkExecutables and findBundles are kinda of suspicious - definitely a KDE Mac specific issue. Here are the missing traces from the second thread. This time I sampled a running kdebudialog.app opened via open /Applications/KDE4/kdebugdialog.app
@boud - thanks for your reply on the kde-imageshop archive I will post on kde-mac to see if anyone can help. And yes, this is kinda bleeding edge (I'm a glutton for punishment) but I have to say that I'm very stuck at the moment. Becoming a KDE expert is not my ultimate goal as I am eagerly waiting to plunge into Krita! Very frustrating up till know, but it's only my third day drinking from this fire hose... I've also printed all that kde4-config reports (below):
On a more Calligra based topic. I managed to get all of Calligra (Creative)to compile and given my KDE woes figured I might tackle debugging the ****. My IDE of choice is Xcode 4.2 ( I know...u guys hate the Mac with a passion but the recent beta cut has come a really long way ) So ran the CMake Generator and can report the following: 1 - Out of the box a CMake -G Xcode on Calligra generates unusable Xcode project files. They don't parse. 2 - After a little I digging discovered that some paths are not escaped correctly for Xcode and CMake stumbles. Here are the offending lines and some suggested fixes: In my KDE4Macros.cmake...(not sure which project installs)
In Various test CMakeLists.txt
Again another KDE related issue so I'm not sure where and how to report. I compiled Calligra from the command line to make sure they didn't break anything. Just though this my help someone out there... Also had a few problems with boost (from macports) not getting picked up correctly so had to hardcode include_directories(/opt/local/include ) in some CMake files. Same with marble and tiffio... I hope, my luck improves... Later, Patrice |
|
Administrator
|
When compiling, which components did you build? Qt, kdelibs.... make sure kde-runtime is also built.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Yahoo!!!
Success. Finally. After three sleepless nights I have all Qt, KDE and Calligra apps up on Mac OS X Lion. Seems fitting as it (Lion) is now officially released ;-) Now I can actually talk about it without the evil empire lawyers on my back... Mark this day July 20 - Krita lives on Lion! And all from the development branch, no macports or fink (which doesn't yet work on Lion) In my frenzied attempt to get things up and running I started to lose a bit of my own discipline, so I'm not totally sure what bootstrapped it up. Here are some preliminary notes: - A closer look at my own trace and I focused on the mac_initialize_dbus() kernel_mac call since all apps seemed to hang on that. - Noticed that QtDbusViewer, while functional, could not connect to dbus (macports), so I rebuilt qt-kde with some new switches and full debug. Will expose my config switches once they are set. Anyway, got Qt to a point where the dbus introspection worked. I think I rebooted once. Not sure but it was obviously a good first step. - Rebuilt all of KDE methodically. Starting with kdesupport (automoc, attica, phonon in QTDIR, PolKitQt and kdesupport-svn) All using the "easy" recipes when I could. Then kdebase (runtime, kate, and console) Followed by kdesdk. Finally kdelibs. Never got kdepim to fully build, but doesn't seem to be a requirement for the "Creative" Calligra suite. - Still no go. And somehow even switching debugfull did not output anything to console. So I wrote a little kde test app with custom kapplication and kkernel_mac so I could freely debug. Not bad for a few days drinking from the firehose. That's when I noticed the following error followed by failed attempts at invoking drkonqi. This is still not fixed. More later.
- A little more digging and realized my XDG_DATA_DIRS wasn't set correctly so adjusted to
- Also had to make sure my DYLD_FALLBACK_LIBRARY_PATH was set correctly. Otherwise attica and dbusmenuqt dylibs were not found (?) Not good . Here's a script to set up my apps correctly
- Ran Krita and got a screen WooHoo! But blank...(sigh) Finally had debug messages and figured my db was not up to date. So... - Ran kbuildsycoca4. Complains a lot (as usual ?). The KDEHOME variable had to be set to something other that $HOME/kde/.kde. Not sure why either. - Ran kdebugdialog successfully...good omen... - Finally got the Krita up and running via simple open/Applications/KDE4/krita.app! And others like carbon... Sorry for the gory details. Some (if not most) of this is probably familiar, but for a noob digging around the myriad of docs and red herrings along the way, I thought it would be helpful. Some Initial Observations: - crashes a lot in debug - very sluggish. I know it is a debugfull but I am running on an octo MacPro ... will try Release soon. - yes the interface needs a little work ;-) IMHO not up to Mac standards...doesn't do this justice really. - Along the way, I noticed that some of my builds broke running in parallel (make -j16 or even -j9). Fixed by running single threaded especially kderuntime and even kdelibs in a specific order. Wha a waste of horsepower. I will investigate further...Ultimately the order should not matter. CMake issue? I want to do a few things next, before actually popping open the code hood: - Run through this again, on a clean install of everything - Document the steps with additional details for others (like build configurations, environment settings, make and install output) I know Yet Another How-To on Mac builds may cloud the sphere, but I'm sure I'm not the only one getting lost in all of that sauce...;-) Still very worth while climbing that mountain. A trial by fire, right of passage? ;-) - Run a full release build and test - Post screen snapshots - Set up an Xcode IDE and tune the CMake -G Xcode output (see previous posts) - Start looking at performance with tools like Shark etc... - Experiment with Apple's llvm30 compiler - develop a full build script -- Ok I know that's bold. But eventually a Mac OS X nightly build dashboard like you have for Windows would be nice. I would volunteer a dedicated server and status page on my end if interested. Again, may be a long term plan. Just a few thoughts and ramblings in no particular order struggling with fatigue. Will organize this later and maybe open a new Lion thread with structured observations and steps. As usual your thoughts on how best to move on and get the Mac side going are welcome...(the initial ones from boud were good!) This is great! Krita on 64 bit Lion with beta Xcode 4.2 system libraries and tools. Back on the horse... Thanks for all your help, Later Patrice |
KDE Developer
|
|
|
Registered Member
|
|
|
KDE Developer
|
Interesting that the new and open buttons don't have icons, but save has. You should make the window a bit bigger so the rest of the toolbar fits into the window.
|
|
Administrator
|
The lack of icons could be related to the KSharedDataCache message you recieved earlier. Not sure if KDE on Mac uses similar paths to Linux, but if it does....
1) Make sure all KDE related processes (kdeinit4, klauncher, etc) aren't running 2) Remove /var/tmp/kdecache-$USER/ 3) Run "kbuildsycoca4 --noincremental"
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Yup. Clearing out the cache (btw it's in /private/var/tmp/master-kde on my system) worked and restored all the icons after a sycoca. And yes full screen is a much better view.
I won't pretend to know Krita yet, but there is a preview box for the layers dock that won't go away seems like it is missing some close buttons. Also all the top menu items disappear when that happens. I'm also tracking klauncher's inability to launch knotify4. It seems like this cut packages it as a mac bundle (in /Applications/KDE4/knotify4.app when it may best reside in lib/kde4/libexec? I built the master branch so no surprises here about these glitches. Patrice |
|
KDE Developer
|
|
|
Registered Member
|
Thanks.
Out of curiosity, what is the predominant IDE in the development group. KDevelop? Eclipse? CodeBlocks? Others? Do you have a standard toolchain+Ide? Patrice |
KDE Developer
|
I prefer KDevelop, some prefer Qt Creator
Daylight is coming...
Krita developer | http://lukast.mediablog.sk/log |
|
KDE Developer
|
I use vim and Qt Creator -- and compile in a terminal
|
|
Registered Member
|
Ok
I'm even closer to having a full development environment/workflow set up: -I have a KDevelop 4.2.3 up and running. It has a few quirks that I've informed kdevelop-devel about. -Also have Eclipse/Indigo setup. A little more stable, yet more of a pain to configure for CMake KDE projects. At least I can debug Krita on it. -This may allow me to put the Xcode project on the back-burner. I have to admit that I'm pretty amazed that Mac/Darwin support is so poor all across the board. It really isn't that bad, and if the goal is cross-plarform apps than how can one totally ignore this platform. I'm not a total Mac fanboy and my roots deeply lie in Unix back before Linux was even a word. So I'm willing to get my feet wet TESTING also. Besides, from the looks of it the team seems composed of some very able and talented individuals and it will take me a little while to fully absorb the underlying design and architecture. So off to reading all the design documents on the Krita site... To better support testing a parallel Linux-based environment is "de rigueur". I can run one side by side with the Mac using Parallels. The choices are many, but I am leaning towards Kubuntu or Open SUSE. Which do you recommend? I'll follow you're suggestion about native features via plug-ins "ala" openCL and OpenGTL OpenShiva. Very interesting stuff indeed. On memory usage - you do implement a tiling concept already. Are there any particular modules that are worth inspection? In my experience tuning memory and performance on large projects like this, defining the actual system and performance requirements is critical. This is not a small app and its loaded with neat features (especially like the custom brushes), what are the expectations? All this needs to be balanced with the proper design. Its always a trade-off between features and performance. Hardware always moves faster. Photoshop like performance is a nice goal, then again those guys have large corporate resources at their disposal... On the Mac visuals - aside from the layer dock icons that seem a little jumbled (I would have to compare this to the Photoshop layer interface), I think the UI must have come a long way from your original post a few years ago cause it's not that bad. I would say consistent with a KDE/QT interface paradigm and since the underlying architecture is based on it...On the other hand, there is obviously a lot to be said about a professional Mac like look & feel on this platform. General consensus is that Apple does that very well and most of their software follow their guidelines pretty closely. I don't want to start a flame here about UI/UX concepts, but this begs the question of how mac specific you want this distribution of Krita to eventually look. IMHO, "as much as possible" simply because a Mac artist considering Krita will naturally expect things to "feel" the same. And this is all about the users right? But of course this would require a complete redesign of dialogs and forms to be consistent, not just the file manager. Getting back to where I can help in the immediate future - are there any particular features or modules you would like me to test on this platform? If so, just holler... Meanwhile I am still looking into some build issues and utility bundling that doesn't seem to make sense on the Mac... @Lukas - I really enjoy reading your blog on Krita... Later, Patrice |
(???)
) <7DA8E59F-2711-3BDA-9882-987FAF606102> /Applications/KDE4/kdebugdialog.app/Contents/MacOS/kdebugdialog
<3AD29F8D-E3BC-3F49-A438-2C8AAB71DC99> /usr/lib/libcrypto.0.9.8.dylib
Bookmarks
Who is online
Registered users: Bing [Bot], gfielding, Google [Bot], markhm, sethaaaa, Sogou [Bot], Yahoo [Bot]
