This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Linking against shared library linked to another shared one, please help

From: Ian Lance Taylor <ian at airs dot com>
To: matteo dot pampolini at seleniacomms dot com
Cc: binutils at sources dot redhat dot com
Date: 10 Mar 2005 10:59:52 -0500
Subject: Re: Linking against shared library linked to another shared one, please help
References: <OF94DF21A7.7DE1B456-ONC1256FC0.0054A820-C1256FC0.005587B0@SeleniaComms.com>

matteo.pampolini@seleniacomms.com writes:

> Ok, suppose a C app links against shared libAAA that in turns links against
> libBBB:
> why should I tell app of libBBB presence?
> 
> If I want to hide the implementation of libAAA and eventually later change
> it, I should be
> able to avoid putting this information inside app compilation process,
> isn't it?
> 
> I had a look at ld man page in -rpath-link section, but it seems to me that
> it doesn't
> fit my needs.

Why not?

Ian

References:
- Linking against shared library linked to another shared one, please help
  - From: matteo . pampolini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]