Hello, Sorry that the bug got unattended for long, I took over the package later than it was submitted and didn't put much attention to it because there were other pressing issues and no seconding to your request.
Apart from that, I researched the topic a while ago and people seem to have mixed experiences with static build in Unix systems. Finally I asked upstream explicitly about this and got the following reply: ------------------------------------------------------------------------------------------ > 2) There are people that request that we provide also static versions > of the libraries. Could you please tell me if it's a > recommended/supported thing to do, or it's known to cause problems > (maybe only in some architectures)? We do support static compilation, but it's not the default and is not tested as rigorously. I think a couple of people use static builds on Windows, the situation on Linux may be less stable. Personally I think whoever wants to build against a static version of Ogre should compile it himself :) But if you want to provide them: To enable static builds, the CMake variable OGRE_STATIC must be enabled. ------------------------------------------------------------------------------------------ So I don't know if we should do that in the Debian packages, especially knowing that we hit many more architectures and for much longer time than anybody else. Additioanlly, compiling the libraries statically for Debian packages is not as straightforward as adding a switch: we have to modify debian/rules to compile twice in the same building process, one with static libraries and with shared. I know from similar packages that this is complex, and it puts quite a lot of strain in the building machines. So at the moment I am a bit reluctant to go on this path. Cheers. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
