Hi, For some time, Simgear has had the option to build shared libraries (DLLs on Windows) - this is only really useful for developers, since it can reduce link times. However, when I made this change, I organised Simgear into 'core' and 'scene' libraries; the 'core' part is also what we call 'headless' simgear, i.e can be compiled without requiring OpenSceneGraph or any GUI systems. (Which is how SG is used by terragear and potentially some other users).
Mathias has suggested, and I agree, it would be sensible to also package the *static* libraries this way. So instead of having many static libraries, we will have only two: libSimGearCore.a and libSimGearScene.a This will likely mean some small changes to the CMakeFiles for the downstream projects; I will take care of FlightGear and TerraGear directly, and will of course help fix any other affected code. Any comments or objections on this change? Note this DOES NOT increase the linked binary size of executables created from SimGear - linkers already discard unreachable code when linking against .a archives. All we're doing is giving the linker one .a to unpack into objects, instead of a group of them. James ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
