laverdet/node-fibers — Issue #37: Static linking for coroutine ?
Author: jbaron
Created: 2011-10-08 07:16:45+00:00
State: open

Great library and improves maintainability of my app lot (which is a very important aspect in a larger application in IMHO).

However moving this module around is tricky due to the fact that fibers.node is linked to the fullpath of coroutine.so. For example the ldd output:

ldd fibers.node
linux-gate.so.1 => (0x00cee000)
**/home/dks/src/node-fibers/src/coroutine.so (0x003a0000)**
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0x00ed9000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0x009a5000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0x00110000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00a9c000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0x00653000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0x00ebe000)
/lib/ld-linux.so.2 (0x00767000)

Would it be possible statically link coroutine.a so we could just move fibers.node around and don't have to worry about other files (or provide this as an option in the Makefile at least)?