[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-mac
Subject:    Re: [KDE/Mac] Fixes for Filelight utility and LSkat game
From:       mk-lists () email ! de
Date:       2014-05-10 0:20:35
Message-ID: 5B94D2E5-2032-4E8D-8C72-D60FD1FDFB3F () email ! de
[Download RAW message or body]

Hi again,

On 09 May 2014, at 19:31 , Nicolas Pavillon <nicos@macports.org> wrote:
> > Currently kde-runtime, kde-workspace and kde-baseapps fail to build.
> > kde-runtime is getting a linker error in kglobalaccel (keystroke and shortcuts
> > handler).
> > 
> > Linking CXX executable kglobalaccel
> > Undefined symbols for architecture x86_64:
> > "GlobalShortcutsRegistry::keyPressed(int)", referenced from:
> > hotKeyEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) in \
> > kglobalaccel_mac.o KGlobalAccelImpl::keyPressed(int) in kglobalaccel_mac.o
> > ld: symbol(s) not found for architecture x86_64
> > clang: error: linker command failed with exit code 1 (use -v to see invocation)
> 
> This error is not KDE 4.13 specific, we had it for some time (I think it appeared \
> at 4.12). There is a fix in Macports to circumvent it. However, it is not a simple \
> patch, but  a post-configure hack, which can be applied manually, although it may \
> be cumbersome. 
Oh, I see, there is a patch in place for KDE 4.12 regarding kglobalaccel…
Any chance that the different behaviour of kglobalaccel on OSX 10.6.8 and OSX 10.9.2 \
[1] could due to that?


> > Note that I have a MacPorts installation that I use for everyday activity
> > so I do not want to risk messing that up.
> 
> If you don’t need them simultaneously you could keep the two installation around,
> and use activate/deactivate commands to have the one you want at a given time. 
> For simultaneous use, having two separate Macports tree may also be possible, 
> but it is signing for trouble in my experience.
Oh yes… Both opportunities aren’t great!
For endeavours like that it’s better to have a KDE-build on a virtual machine, or on \
another real machine. Otherwise you’ll ask for trouble, since a painless deactivation \
and activation might be hard to achieve due to dependencies on a lot of other ports. \
And on top of all that all your config files from one KDE version would be \
interfering with those of the other, since they get stored in \
~/Library/Preferences/KDE/...

Greets,
Marko



[1] https://bugs.kde.org/show_bug.cgi?id=334174
_______________________________________________
kde-mac@kde.org
List Information: https://mail.kde.org/mailman/listinfo/kde-mac
KDE/Mac Information: http://community.kde.org/Mac


[prev in list] [next in list] [prev in thread] [next in thread]