On Tuesday 17 October 2006 13:35, Holger Freyther wrote:
SVN commit 596397 by zecke:
runtime/kioslave/smtp: Link to QtNetwork to fix link issues on OSX/Darwin
M +1 -1 CMakeLists.txt
--- trunk/KDE/kdebase/runtime/kioslave/smtp/CMakeLists.txt #596396:596397
@@ -90,7 +90,7 @@
David Faure wrote:
How can we fix KDELibsDependencies.cmake to also include indirect
dependencies?
We shouldn't. Why should we care whether Qt links to Xrender? Or if
libxslt uses libexpat?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358;
On Tuesday 17 October 2006 14:20, Thiago Macieira wrote:
David Faure wrote:
How can we fix KDELibsDependencies.cmake to also include indirect
dependencies?
We shouldn't. Why should we care whether Qt links to Xrender? Or if
libxslt uses libexpat?
Well, see the message I was replying to -
David Faure wrote:
On Tuesday 17 October 2006 14:20, Thiago Macieira wrote:
David Faure wrote:
How can we fix KDELibsDependencies.cmake to also include indirect
dependencies?
We shouldn't. Why should we care whether Qt links to Xrender? Or if
libxslt uses libexpat?
Well, see the message I
David Faure wrote:
I understand what you're saying - if it uses QtNetwork it should link
directly to it and not via kdecore. I agree with this, conceptually.
But the practical problem is that on Linux it all links just fine via
kdecore, so the developers will never remember to add such explicit
On Tuesday, 17. October 2006 15:32, David Faure wrote:
But the practical problem is that on Linux it all links just fine via
kdecore, so the developers will never remember to add such explicit links,
since it works for them (tm). So the guys doing Mac OS (and maybe
Windows) porting will keep
Dirk Mueller wrote:
On Tuesday, 17. October 2006 15:32, David Faure wrote:
But the practical problem is that on Linux it all links just fine via
kdecore, so the developers will never remember to add such explicit
links, since it works for them (tm). So the guys doing Mac OS (and
maybe Windows)
