Doesn't static waste a huge amount of RAM? At least if lots of coins all are static doesn't that stop them sharing code pages for all the libs they all have in common?
We still haven't gotten the RAM hogging fix into all the merged mined coins and already people want to start making them hog more for libs they all use?
Or is there some smarts in the sharing that will notice the static libs are the same and share them?
-MarkM-
We still haven't gotten the RAM hogging fix into all the merged mined coins and already people want to start making them hog more for libs they all use?
Or is there some smarts in the sharing that will notice the static libs are the same and share them?
-MarkM-
no, not any magic that will detect libs static linked into other binarys. the only advantage is redistributing easily and professionally.
Yes Mark you're right, no need to distributed devcoind static, because all those people using devcoind will be sys admins, that they are not likely to use directly binarys and will prefer to build themselves. I think sidhujag may refer to devcoin-qt linux version, instead of devcoind.
I hope so. It gets tiresome having to meddle with the makefiles of all the coin daemons to make sure they all use dynamic linking.
Especially for merged mined coins it makes sense to assume people will run many of the daemons.
-MarkM-
Ok I will change it to link dynamically. But the libs them selves will be statically built to avoid putting in runtime libs sound fair?
I left other makefiles alone expect a dev to fix and give me the updated file for each os.
