Re: [Widelands-public] Widelands and static linking

[Jari H. <jar...@ik...>]

2010/8/17 Janne Johansson <ice...@gm...>:
> 2010/4/17 Timo <tim...@gm...>
>>
>> there seems to be some interest in building static executables of
>> widelands.
>
> [...]
>
>>
>>
>>
>> I think its a good idea to link in SDL and ggz statically. SDL should
>> link be linked with tiff, jpeg, png, ogg, mp3 static but load libX11,
>> libGL on runtime. I think directfb can be disabled in our static builds.
>> It's quite uncommon and someone who has set up DirectFB is bale to
>> compile widelands himself. Libpthread and libdl should be linked
>> dynamically. I am a bit unsure about libc and libgcc. I will run some
>> thest with these.
>>
>> This mail got far too long. Now I am a bit afraid that nobody will read
>> it until here.
>>
>
> I just wanted to add that if you ship static binaries with libz, tiff, jpeg
> and libgcc
> and whatnot, you really need to make sure *all* licenses are compatible,
> since the
> resulting binary will need to be able to fulfill all demands at once.
> /Janne - long time lurker on this list. And license-nut.
>

Hi!

I have worked on static linking for Visual Studio 2008 build and above
mentioned libraries have nice licenses, which practically just require
proper acknowledgments if used unmodified. These acknowledgements
should be in widelands documentation anyway as they don't separate
dynamic or static linking.

Most important is to watch for GPLv3 licensed sources as widelands is
under GPLv2. For example newer gettext libraries are under GPLv3, so
better stay with older ones.

Other issue is that as far as I understand GPL:ed libraries require
providing source code when distributing in object code. If libraries
are built from sources, then distributing statically linked binary
practically requires to distribute the source code for all statically
linked libraries.

Cheers,
Jari