Contratry to prior versions the KXMLEditorPart is no longer available (since Vesion 1.1.3) I *think* but I am not sure. Using app-editors/kxmleditor/kxmleditor-1.1.3.ebuild, the respective files are installed in /usr/lib instead of $KDEDIR/lib: -rwxr-xr-x 1 root root 1.8K Nov 23 10:27 /usr/lib/libkxmleditorpart.la lrwxrwxrwx 1 root root 26 Nov 23 10:27 /usr/lib/libkxmleditorpart.so -> libkxmleditorpart.so.1.0.0 lrwxrwxrwx 1 root root 26 Nov 23 10:27 /usr/lib/libkxmleditorpart.so.1 -> libkxmleditorpart.so.1.0.0 -rwxr-xr-x 1 root root 712K Nov 23 10:27 /usr/lib/libkxmleditorpart.so.1.0.0 /usr/lib however, seems to be ignored by KDE with regard to parts. Reproducible: Always Steps to Reproduce: 1. emerge app-editors/kxmleditor-1.1.3 2. ls -l /usr/lib/libkxmleditor* 3. observe that in Konqueror and Quanta+ KXMLEditorPart is not available Expected Results: KXMLEditorPart should be readily available after merging KXMLEditor ebuild. Either the libraries should be installed in $KDEDIR/lib or /usr/lib be added to the parts searchpath.
Created attachment 44543 [details] logfile of `emerge kxmleditor` on my box configure claims to identify KDE and QT, $QTDIR and $KDEDIR are set correctly it seems. Still the install goes to /usr/lib instead of $KDEDIR/lib.
Created attachment 44545 [details] Output of `emerge info; echo $QTDIR; echo $KDEDIR`
>Either the libraries should be installed in $KDEDIR/lib or /usr/lib be added to the parts searchpath. The latter is correct. If I'm not wrong, we need some code to do this dynamically, to keep the parts apart from other slotted kde versions they're not compiled against.
Isn't KDEDIRS+=/usr enough?
Um, works for me - looks like you're right Dan. I never had a deep look at the kde framework. Just don't have the time to do my 10X on it. Thought there may be an extra env var for parts. One question remains: Are the kparts compatible between kde versions? I mean, if I compiled Kxmleditor against KDE 3.3, but start a KDE 3.1 session, works the KPart w/o any problem? If not, then it's still an (minor) issue. Alexander: If it does not work for you, please set KDEDIRS=/usr in /etc/env.d/99kde-env
carlo: don't know for sure if it works. How it *should* work is that a kpart would link against versioned shared libraries, and so would load the correct ones and run under any other KDE, because all KDEs are available to ld.so in some order. But I don't know if it works 100% or not. If not, ought to be fixed :-) Alexander: please find out why you didn't (apparently) have a /etc/env.d/99kde-env whose contents are KDEDIRS=/usr and which should be installed by the kde-base/kde-env package.
Hmm... I *do* have $KDEDIRS set to /usr: eclipse ~>cat /etc/env.d/99kde-env KDEDIRS=/usr CONFIG_PROTECT=/usr/share/config KDE_MALLOC=1 #KDE_IS_PRELINKED=1 eclipse ~>echo $KDEDIRS /usr However, since -- apparently -- KDE 3.3.1 the part fails to appear. Quanta+ fails to verify it in the plugins configuration until one manually sets the location to /usr/lib. Even then Quanta+ crashes when activating the plugin via the pulldown menu. I did `emerge --emptytree kde && emerge kxmleditor`, without success, so I'd assume my KDE and KXMLEditor installations are as good as new, but no joy... Regarding the compatibility to slotted versions: Well, relative to the shared libs I'm with you guys. Regarding the KParts API I'd think its a safe bet that a part compiled against, say, 3.1 will work in 3.3, but not vice versa. If the API is extended in a minor release (without altering existing interfaces/protocols), things will break if a part depends on one of these new features. Thanks for your efforts! Flexx
I did some research: quanta does not do any automatic scanning for available plugins, the list of plugins is hardcoded in /usr/kde/3.3/share/apps/quanta/plugins.rc. Every new plugin should be configured manually (and the it gets saved in ~/.kde/share/apps/quanta/plugins.rc). For a given plugin file (libkxmleditorpart.la), quanta does a search only if you don't specify the location. In your case, could it be that you have a stale /usr/kde/3.3/lib/libkxmleditorpart.la (bug 64112 ?) that confuses this search. I don't know about the crashes, though.
See previous comment.
