kdefx/blitz options

[Matthew Woehlke]

Matthew Woehlke wrote:
> winterz asked me to post an update on what our options are w.r.t. kdefx. 
> So, here we go...
> 
> [snip]
5. use blitz, fix our build system
   + cleaner code, maintained, up to date
   + no more kdefx anywhere :-)
   + blitz can be removed later (e.g. 4.1), BC
   + porting should be not too bad
   + kdelibs can use blitz

...and shoot anyone that uses blitz w/o -lblitz for abusing ELF (note: 
Windows might not allow such abuse).

I used the attached stuff to test that it should be OK/BC to remove an 
unused lib w/o breaking BC (provided that it isn't spuriously 
referenced, that is).

-- 
Matthew
People say I'm going insane. I say, "what do you mean, 'going'?".
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: app.c
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070813/21a3be58/attachment.c>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: direct.c
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070813/21a3be58/attachment-0001.c>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: indirect.c
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070813/21a3be58/attachment-0002.c>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Makefile
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070813/21a3be58/attachment.ksh>