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 [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
