In stock VM I noted the plugin are not stripped. Does it make sens to strip the plugin, and if so how can it be inserted in the arcane of the Squeak-vm configuration script?
I remember about the -s linker option, but it may break the dynamic linkage, right?
Thanks
Hilaire
On 12/07/10 14:13, Hilaire Fernandes wrote:
In stock VM I noted the plugin are not stripped. Does it make sens to strip the plugin, and if so how can it be inserted in the arcane of the Squeak-vm configuration script?
I remember about the -s linker option, but it may break the dynamic linkage, right?
I was looking into the same topic a few weeks ago. The two papers linked below are very useful and make a clear case for stripping symbols for several reasons, some not so obvious.
Also if the VM build used the "-fvisibility=hidden" compiler option and plugin devs used the following macro for explicitly exports then plugins would be leaner, safer and closer to compiling on Windows (a more comprehensive solution at [3]).
#define DLLEXPORT __attribute__((visibility ("default")))
-D
[1] How to Write Shared Libraries: http://people.redhat.com/drepper/dsohowto.pdf
[2] Good Practices in Library Design: http://people.redhat.com/drepper/goodpractice.pdf
[3] Symbol Visibility http://gcc.gnu.org/wiki/Visibility
vm-dev@lists.squeakfoundation.org