Re: [Qt-interest] LGPL and static linking

[Bastian Bense]

I guess the .a format is, unlike shared libraries, not compatible with every linker. So the user would need the exact version of the toolchain to be 100% sure that re-linking will go smooth.Â

Why not simply provide the user two download options when downloading your application (except, of course, for those cases where it is technically impossible): a dynamic version (possibly hidden somewhere between the links on the download page), and the static variant. So if he/she wants the dynamic version and swap some DLLs, they can do it with the dynamic build, otherwise they can enjoy the static build with the smaller file size and so on...

2009/12/2 <andrew.m.goth@xxxxxxxxxx>

Daniel Grubbs wrote:
> It seems to me that it should be possible to write a
> de-linker which would allow one to turn one's linked program
> back into object files. ÂWouldn't the existence of such a
> program solve this whole problem?

Earlier tonight an off-the-wall idea came to me. ÂDeliver two (or more) .a files (archives of .o files), one of which is your program and the other is static Qt. ÂAlso deliver a simple script to run ld on the .a files to make the executable. ÂNow you can't be accused of making a derivative of the Qt library. ÂIf anyone's making a derivative, it's the customer, and he's doing it without access to your source code!

--
Best regards,
Bastian Bense

_______________________________________________
Qt-interest mailing list
Qt-interest@xxxxxxxxxxxxx
http://lists.trolltech.com/mailman/listinfo/qt-interest