widelands-dev team mailing list archive

[SirVer <SirVer@xxxxxx>]

> I am not sure if this long linking times are perhaps caused by those internal circular dependencies of the widelands code base / sub libs. Even on my system linking a debug widelands.exe takes 5 minutes alone.

Yes, that is the main reason. Basically when you have a cyclic dependency, each library has to appear multiple times on the linking command line and the linker has to keep all symbols of everything in memory. That brings up linking time by a lot. Linking is much quicker though if you build a release binary (less symbols) - one of the reasons I rarely build in debug mode. 
-- 
https://code.launchpad.net/~widelands-dev/widelands/appveyor_linking_memory/+merge/302275
Your team Widelands Developers is subscribed to branch lp:~widelands-dev/widelands/appveyor_linking_memory.