I'm not sure what is meant by 'kernel accessing functions' in the context of static linking. However that's not what I was referring to. I was referring to static linking being incompatible at the user code level. Ie, gcc doesn't allow '-static' and '-shared' at the same time, and if you force it using a linker line you end up with competing heap managers which will crash with code that uses dynamically allocated memory.
At 2006/05/06 06:52 PM, Alfred Reynolds wrote: >You are right, we do exactly that for HLDS and Source. You cannot do a >full static link however as the embedded kernel accessing functions then >crash on incompatible machines. > >- Alfred > >Jorge Rodriguez wrote: >> [EMAIL PROTECTED] wrote: >>> If you're using a newer version of gcc than the version the host box >>> came with, you may need to ship libstdc++.so, libc.so or others with >>> your game .so. GNU/Linux does an absolutely abysmal job of helping >>> you in this respect. There is, for instance, no way to fully >>> statically link a dynamically linkable library. >>> >> I was under the impression that you could link in libstdc++.a, and >> that >> would let you distribute your binary onto a box with an incompatible >> version of GCC. Correct me if I'm wrong. >> >> -- >> Jorge "Vino" Rodriguez >> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list >> archives, please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlcoders > >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, please >visit: >http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
