Tor Lillqvist <tml@xxxxxx> wrote, in reply to Martin Dolezal: > ... apparently is not Free Software. That is not a problem, you can still > use dynamically linked (DLL) LGPL libraries just fine. >> You have to distribute libraries source code if you are asked to do so by somebody > And not just "somebody", but somebody who has acquired the > corresponding binaries.... ... > Note that there is no need to provide "technical support" though, as > long as you distribute the source code in a reasonable format, in the > same format as you or whoever built the library binaries used it, with > the same configury and makefilery etc, Hmm. I finally got my Win32 cross-compile working on Linux, and thought I understood this, but now I'm not so sure. So if I want to distribute a closed-source GTK+/Cairo Windows app, I can package, for instance, my .EXE and Tor Lillqvist's Win DLLs, but I must include the DLL source and build environment? Could I fulfil that by packaging Tor's bundle from http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.16/gtk+-bundle_2.16.6-20091013_win32.zip ? I remember reading somewhere that I needed to ship my object code, so that it could be re-linked against newer or changed versions of the libraries. Is that true for GTK+ and associated libraries? Alternatively, can I comply with the LGPL by shipping just my EXE and require the recipient to acquire the DLLS, say from the GIMP installers? Thank you John Mills _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
