static vs dynamic linking
From: James Autry (j.m.autry_at_Austin.rr.com)
Date: 02/18/05
- Next message: Grant Edwards: "Re: static vs dynamic linking"
- Previous message: Lew Pitcher: "Re: compiling stuff"
- Next in thread: Grant Edwards: "Re: static vs dynamic linking"
- Reply: Grant Edwards: "Re: static vs dynamic linking"
- Reply: Jonathan Bartlett: "Re: static vs dynamic linking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 18 Feb 2005 04:22:05 GMT
What is the best way to build a C non-open source app ( due to proprietary
info contained therein) that can be used across SUSE and RED HAT. I had
heard that statically linking the system libraries gives some assurances,
then I heard that installing the dynamically linking and installing the lib
with the app is another way. How is this normally handled?
- Next message: Grant Edwards: "Re: static vs dynamic linking"
- Previous message: Lew Pitcher: "Re: compiling stuff"
- Next in thread: Grant Edwards: "Re: static vs dynamic linking"
- Reply: Grant Edwards: "Re: static vs dynamic linking"
- Reply: Jonathan Bartlett: "Re: static vs dynamic linking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]