Static Linking and Library Dependencies

Static Linking and Library Dependencies

[Browder, Tom]

Say I have two static libraries A and B.

In A there is only one function, foo, that depends upon B.

My program uses functions in A other than foo.  

Is there any way to link my program with A but not have to link B also?

Thanks.

-Tom

Tom Browder
Nicevile, FL

Re: Static Linking and Library Dependencies

[Nick Clifton]

Hi Tom,

> Say I have two static libraries A and B.
> In A there is only one function, foo, that depends upon B.
> My program uses functions in A other than foo.  
> Is there any way to link my program with A but not have to link B also?

Yes.

I am tempted to just leave the answer there, but I will be nice.  If the 
other functions in A which are used by your program are in different 
object files within the library then B will not be linked it at all, and 
  you will not have to do any extra work.

If there are functions in A which are used by your program and which are 
in the same file(*) as foo then you have two choices.  If you have 
access to the sources for A then you can recompile it with the 
-ffunction-sections switch and then link with the --gc-sections switch. 
  This should allow foo and its dependencies in B to be discarded by the 
linker.  (Alternatively you can hand edit the sources for A so that foo 
is compiled in its own file).

If you do not have the sources for A then you can create a dummy version 
of the B library that is empty apart from the symbols needed to satisfy 
the references in foo().  Then you can use this dummy library in place 
of B.  This solution is not as elegant but it should work.

Cheers
   Nick

(*) Strictly speaking I should be talking about "compilation units" here 
rather than "files".

RE: Static Linking and Library Dependencies

[Browder, Tom]

> -----Original Message-----
> From: Nick Clifton [mailto:nickc@redhat.com] 
...
> Yes.
> 
> I am tempted to just leave the answer there, but I will be 
> nice.  If the other functions in A which are used by your 

Thanks, Nick, that's very helpful.

The problem for me has been that the intimate details of linking and
loading are scattered in pieces all around the net.  The GNU manuals on
gcc, ar, ld, and libtool help but most of them assume knowledge that the
reader may not have who just happily does "./configure; make; make
install."  Ulrich Drepper's papers also help, but again dive too deeply
for me too quickly.

I would be happy to buy a good textbook on the subject if you have a
suggestion.

Thanks again.

-Tom

Re: Static Linking and Library Dependencies

[Eric Christopher]

> I would be happy to buy a good textbook on the subject if you have a
> suggestion.
> 

Textbooks for this are in short supply :)

About the only suggestion would be "Linkers and Loaders":

http://www.amazon.com/gp/product/1558604960/sr=8-1/qid=1153236559/ref=pd_bbs_1/103-9595114-2289464?ie=UTF8

-eric