Quote:
Originally Posted by NiLuJe
@knc1: I (almost) never *completely* link statically. At best I statically link one or two troublesome or recent lib, but I usually try to use mostly dynamic linking, while avoiding ABI/API mismatches, (like this one, which wouldn't even be an issue if I was building against the same glibc as the Kindle, which is what I'm doing on my K5 TC  ). |
I agree.
I was not recommending statically linked applications over dynamically linked applications.
Perhaps I wasn't clear - - -
I was only recommending against trying to statically link applications against glibc rather than any of the several libc's that are designed to support that purpose.
I know I haven't posted enough applications here yet for a pattern to be evident, but I am only statically linking occasionally used utilities where the un-shared memory usage penalty will be rare since they are rarely used.
I have a couple more on my todo list, but by the time I have finished those, there should be plenty of examples of how to do it.
Complete with everything a person needs now or in the future to duplicate the work.
I.E: Work done in the sense of a collaboration with the community at large, not in a competition with the community or any of its members.