Making kdefx static

Alexander Neundorf neundorf at kde.org
Fri Aug 3 22:43:38 BST 2007


On Friday 03 August 2007 16:34, Matthew Woehlke wrote:
> Thiago Macieira wrote:
> > 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.
>
> Well obviously we need to fix that :-). 

Bill tried to get convenience libs working, but it failed on some compiler 
(XCode or MSVC) so cmake doesn't support it. 
There is a test for it in cmake which is disabled (because it is not supported 
now).
Even if a future cmake version would support it, we couldn't use it for KDE 
4.0, because we require cmake 2.4.5.

Bye
Alex




More information about the kde-core-devel mailing list