Making kdefx static

[Thiago Macieira]

Andreas Pakulat wrote:
>> Therefore, I can think of a few options:
>> 1. Rename the useful bits K3* and remove what we can
>> 2. Make the library static
>> 3. Both?
>>
>> Option 1 would mean we are stuck with stale (and ugly) code for the
>> life of KDE4. Option 2 means we can yank kdefx later without affecting
>> BC. Option 3 is the same as 2 except that 2 is (or is very nearly) SC,
>> while 1 and 3 require minor code changes for all users (i.e. adding
>> "3" to all uses).
>
>As far as I know the plan is to introduce Blitz from Mosfet as
>replacement for kdefx in KDE 4.0 and replace that by Quasar for 4.1
>(when its ready). Blitz would be created as static library so its easier
>to remove later on and AFAIK Mosfet wanted to help in the porting
>effort. This would allow to svn rm kdefx completely for kde4.0

Forget "static".

You can't link a static library to a dynamic library.

Leave it a normal, dynamic, shared library. Just don't install the headers 
and remove its finding from the KDE cmake macros.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070803/ab51b501/attachment.sig>