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

List:       kfm-devel
Subject:    Re: kwebkitpart and konq-plugins dilemma...
From:       Dawit A <adawit () kde ! org>
Date:       2010-02-27 18:00:29
Message-ID: 201002271300.30201.adawit () kde ! org
[Download RAW message or body]

On Saturday 27 February 2010 12:54:16 Dawit A wrote:
> While attempting to go through and fix some of the Konqueror plugins to add
> support for kwebkitpart, I run into one dilemma I do not know how to fix.
> 
> Unlike the khtml part, which is available by default, the kwebkitpart is
> optional and must be installed from extragear/base. For that reason some
> checks must be added to the plugins to detect the presence of kwebkitpart
> in order to add support for it. Unfortunately, both the kwebkitpart and
> konq- plugins modules are both located in the very same module,
> extragear/base. This means that in order to activate support for
> kwebkitpart, one must first compile and install kwebkitpart and then do a
> clean (read: rerun cmake) compile and install of the konq-plugins.
> 
> I am sure this is mostly going to be an issue for distro packagers and
> those that compile KDE from source, but still it is an issue and I cannot
> think of a good way to solve it... Is creating dependencies between two
> standalone modules in extragear allowed ? Perhaps kwebkitpart belonged in
> extragear/libs after all ???

I just realized that putting this library in extragear/libs does not help the 
kget konqueror plug-in in kdenetwork/kget. Oh well...
[prev in list] [next in list] [prev in thread] [next in thread]