Trying to compile nedit-latest-sources-HEAD

Thomas Orgis thomas-forum at orgis.org
Sat Oct 7 00:07:38 CEST 2006


Am Fri, 6 Oct 2006 23:03:48 +0200
schrieb Thorsten Haude <yoo at vranx.de>: 

> I think the reason for preferring static links is that they are
> somewhat more reliable if you move the binary around. That's usually
> not a problem on solid distributions, but I have to work on more than
> one platform and appreciate any dependency which does not exist.

Well, the nedit linux Makefile does only link motif statically.
If I want to move a binary around (or share one binary between different
systems via network share) I try to make it as static as possible.
I link _everything_ statically, down to libc.
I understand that the only-motif-static treatment is because one doesn't
want to risk runtime linking with an incompatible motif (lesstif) lib
and I totally understand it for the official binary.
So, I don't wanna press it here... just thought that the people who
download the source instead of the binary might want to run the built
nedit on the box they built it on; or at least have a clue about libs
and linking themselves.
But my starting point was the experience of nedit not building because
the standard openmotif install did not install static libs but only
dynamic ones.

Just to have it mentioned...


Thomas.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.nedit.org/pipermail/discuss/attachments/20061007/dfcbe2f9/attachment.bin


More information about the Discuss mailing list