cygwin-patches for kde 3.4.1

[David Faure]

On Friday 17 June 2005 15:01, Thiago Macieira wrote:
> On the other hand, suppose you linked to KIO, but used something from a 
> library libkio uses directly or indirectly (let's call it third-party 
> libxml). If KIO ever stops using that library, for whatever reason, you 
> program will fail to link. Not only that, it will also fail to run if you 
> upgrade libkio, without touching the program.
> 
> Hence the need to specify all dependencies. 

Sure, for third-party libs used by the app I totally agree. 

> That might be feasible for kdelibs, but might be really hard for other 
> modules and applications unless we create an equivalent .la file.

Yes I was only talking about kdelibs. We know that kio needs kdecore,
and we know that this isn't going to change tomorrow.

> If we do that, we end up at the other end of the problem: every library 
> will be listed. I don't want every library to be linked against: I want 
> only those that my program uses.

Sure.

> The same rationale for libxml can be used: if I don't use libxml in my 
> KIO-using program, why should my program explicitly link to libxml? In 
> special, if KIO drops libxml (for whatever reason, directly or 
> indeirectly), my program should automatically stop loading libxml.
> (The behaviour of the last paragraph is accomplished by ld's --as-needed)

Agreed.

> The linker should solve this here.

It does on linux, but I thought the conclusion was that it can't do so on cygwin?

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).