public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: Soubhik Bhattacharya <soubhik@cse.iitk.ac.in>
Cc: binutils@sources.redhat.com
Subject: Re: Shared Objects and Dynamic Link Libraries
Date: Mon, 04 Jun 2001 09:57:00 -0000	[thread overview]
Message-ID: <sin17o5gjt.fsf@daffy.airs.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106031439120.6805-100000@cseproj22.cse.iitk.ac.in>

Soubhik Bhattacharya <soubhik@cse.iitk.ac.in> writes:

> i have to ask something which is very trivial to many of you...
> what is the basic difference between shared objects and dynamic link
> libraries (if there's any)? it'll be highly appreciated if you refer me to
> good online documentations for libraries, linkers and binary formats
> (relocatable, static, shared, elf, coeff, a.out etc etc).....

Your question is somewhat vague.  I will provide some general
information.

``Shared object'' is a term often used with ELF.  It means the same
thing as ``shared library.''  ``Dynamic link library'' is a term often
used with Windows.  It also means the same thing as ``shared
library.''

There are differences between the ELF and Windows implementations of
shared libraries.  Basically, the Windows implementation is more
primitive: it requires using different source code for references to
global variables, depending upon whether they are referenced in the
main program or in a shared library.  Windows also does not support
overriding a function defined in a shared library from the main
executable.  The only advantage of the Windows approach that I can
think of is that it saves an instruction or two per function call
within a shared library.

I am not aware of any single source for online documentation of
libraries, linkers, and binary formats.

Ian

      reply	other threads:[~2001-06-04  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03  2:25 Soubhik Bhattacharya
2001-06-04  9:57 ` Ian Lance Taylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sin17o5gjt.fsf@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sources.redhat.com \
    --cc=soubhik@cse.iitk.ac.in \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).