Re: Fwd: KDE/kdebase/libkonq
Von: Thiago Macieira [EMAIL PROTECTED] Benjamin Reed wrote: On 3/2/06, Thiago Macieira [EMAIL PROTECTED] wrote: On ELF systems using dynamic libraries, where such nonsense is not necessary, don't install the dependency libraries. To our Windows developers: how does MSVC solve such nonsense? Can it link to a DLL without requiring that DLL's dependencies to be listed? Or does it require you to know what dependencies a DLL has? On OSX you have to list all depends, as long as you're using symbols from the dependent library (even indirectly). Which is braindead. Sorry, but it is. If I upgrade a library I use in my simple program and it adds a new dependency, I have to review my program's ld flags. For such brain-damaged systems, the installation of an .la file is a requirement. I don't think this is needed on win32 - otherwise we would had to link kdelibs against win32 system libs what we're not doing. Christian -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Fwd: KDE/kdebase/libkonq
On Thursday 02 March 2006 15:11, Thiago Macieira wrote: Benjamin Reed wrote: On 3/2/06, Thiago Macieira [EMAIL PROTECTED] wrote: On ELF systems using dynamic libraries, where such nonsense is not necessary, don't install the dependency libraries. To our Windows developers: how does MSVC solve such nonsense? Can it link to a DLL without requiring that DLL's dependencies to be listed? Or does it require you to know what dependencies a DLL has? On OSX you have to list all depends, as long as you're using symbols from the dependent library (even indirectly). Which is braindead. Sorry, but it is. If I upgrade a library I use in my simple program and it adds a new dependency, I have to review my program's ld flags. For such brain-damaged systems, the installation of an .la file is a requirement. So does this mean if I link to kparts and use QString in my app, I have to add QtCore explicitely. But as long as I don't call any functions from zlib directly, I don't have to add it, right ? Seems bearable to me. This would mean la files are not required. Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Fwd: KDE/kdebase/libkonq
Alexander Neundorf wrote: But I don't think we should do that. Yes, but adding these libs would be no problem in kdelibs/cmake/modules/FindKDE4Internal.cmake . That's not what I meant. Yes, please add them to the kdelibs files. What I meant was that the author of an application outside kdelibs should remember to add QtCore, kdecore, kdeui, etc. to his own dependency list. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 2. Tó cennan his weorc gearu, ymbe se circolwyrde, wearð se cægbord and se leohtspeccabord, and þa mýs cómon lator. On þone dæg, he hine reste. pgpKxwJeITNHz.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
