[KDE/Mac] Potential blocker in kdeinit5 and klauncher5 on OS X
iandw.au at gmail.com
Wed Feb 4 20:39:49 UTC 2015
On 05/02/2015, at 3:11 AM, Jeremy Whiting wrote:
> I would be very interested in this fix. You say you already did the fix on kdelibs?
No, I did not. I worked out what was causing the block in kdeinit4 on OSX, but
I was trying to get help to take the whole complex of kdeinit4 and friends further
on Apple OS X. AFAIK, they have never worked as intended on Apple OS X.
But no help was available, so I shelved all the issues. I am now reviving them.
> If you can point me at the commit I can take a look at doing the same on frameworks
> if you want.
I have a full day of non-KDE activities ahead of me, but I will see if I can rough
out a tentative patch this evening or early tomorrow (Friday). That will be daytime
Thursday in the USA (roughly). I am on UTC + 11.
> Since I can build and test while doing it here.
Yes, that would be good. I think the same problem will also happen in Windows.
To check if we have the problem in kdeinit5, insert a log message after the code
that starts klauncher5 (i.e.insert after "handle_requests(d.launcher_pid); // Wait for
klauncher to be ready", around line 1784). Start kdeinit5, with NO klauncher5,
kded5, kdeinit5 or alias of kdeinit5 already running. Might be an idea to have
a log message before "start_klauncher();" too, just to make sure kdeinit5 is
actually entering the relevant block of code.
If your log message fails to appear, kdeinit5 is blocked. It will fail to go on to do
other initialisation things, but it will have started klauncher5.
My investigations into kdeinit5, klauncher5 and friends and the problems they
meet on Apple OS X have reached a point where I really need to have some
running code in which to put log messages, etc. so that I can see more clearly
what is going on in there.
Jeremy, could you write to me privately and let me know exactly how you managed
to build Frameworks/KF5 on Apple OS X?
Like you, I have a kdesrc-build setup. So far, I have source-code for Frameworks,
but no build and no Qt 5. I guess the CMake options would be the main hurdle.
Cheers, Ian W.
More information about the kde-mac