I have been working on what could be called the OS X Keychain backend for kwallet, mostly on KDE 4 because that's what we have in OS X/MacPorts. It works, except that it has no dBus integration.

Or rather, there's no `walletLauncher` (`K_GLOBAL_STATIC(KWalletDLauncher, walletLauncher)`) object, and I have a hunch that this might explain why (un)locking events seem to go unnoticed. I'm not expecting ever to be able to signal if a wallet's underlying keychain is closed by OS X, but it'd be nice at least one could set an idle timeout and have the wallet be closed through the regular KDE means.

I've copied what seemed the relevant KWalletDLauncher and walletLauncher code from kwallet.cpp to kwallet_mac.cpp, but get linking errors about missing symbols. My changes to the build system did not remove libraries, so I'm thinking I must be missing header file(s).

Can someone give me some pointers, please?

TIA.
René

Meh, squinting a bit more at the exact symbols being missed, I realised that I had simply forgotten to copy over the out-of-line member function definitions for the KWalletDLauncher class ...

Now kwalletd launches, but nevertheless, it seems I still don't get any benefit off it...

Sorry for the lack of responses here, the mailing lists tend to work better for development questions.

Well, I'm quite sure I asked on the kde-mac ML (first, probably) and never got a reply.
It'd be great if a couple more "core KDE developers" would subscribe to that list (or start replying) even though most of the questions there don't apply to Linux nor to the "latest and greatest" KF5 ...

In the event you don't get responses, I would suggest mailing kde-devel, kde-core-devel or kde-frameworks-devel as someone who is familiar with the code in question will likely be subscribed to one of those lists. Unfortunately with the vast number of lists around people tend to limit the number they subscribe to (due to the volume of email generated).

bcooksley wrote:Unfortunately with the vast number of lists around people tend to limit the number they subscribe to (due to the volume of email generated).

I hear you - guess why I haven't subscribed to one of those lists yet ... (or why I'm always gladly surprised when a project has opted for a mailing list system that can also be used through a web interface, without subscribing other than to threads started by oneself).