linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mihai Dontu <mdontu@bitdefender.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: How to write apps dependent on external libraries?
Date: Thu, 13 Jul 2006 19:13:52 +0300	[thread overview]
Message-ID: <44B67140.10208@bitdefender.com> (raw)
In-Reply-To: <200607132134.57378.samjnaa@gmail.com>

Shriramana Sharma wrote:
> Often I see apps which are dependent on this .so file or that. I don't know 
> how apps can be written that depend on libraries that are not linked into the 
> executable. So far I have been linking all needed libraries into the 
> executable.
> 
> A .so is a collection of what? An .a is a collection of .o-s, right? What is 

A .so (Shared Object) is a "collection of code". Basically the code from 
all .o-s is gathered _and_ _linked_ into this file.

> a .la? I am so very confused.
> 

.la is a libtool thinggy which contains different informations about how 
to create/load/link a .so

> I don't know what keywords to search for on Google. Which is why I ask here. 
> If it is a detailed subject please give me keywords so I can search and find 
> on my own.
> 
> Thanks for your help.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 



-- 
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://www.bitdefender.com/


  reply	other threads:[~2006-07-13 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 16:04 How to write apps dependent on external libraries? Shriramana Sharma
2006-07-13 16:13 ` Mihai Dontu [this message]
2006-07-13 16:40 ` Steve Graegert
2006-07-14  0:28 ` Glynn Clements
2006-07-14 10:32   ` Markus Rechberger

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=44B67140.10208@bitdefender.com \
    --to=mdontu@bitdefender.com \
    --cc=linux-c-programming@vger.kernel.org \
    /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 NNTP newsgroup(s).