link with static library vs individual object files

Posted by dododo on Stack Overflow See other posts from Stack Overflow or by dododo
Published on 2010-04-09T18:01:34Z Indexed on 2010/04/09 18:03 UTC
Read the original article Hit count: 270

Filed under:
|
|

For a reason i want to unpack a static lib (libx.a) into individual object files (a.o b.o c.o), and specify these object files (a.o b.o c.o) in the linker input list instead of libx.a, with other linker options remaining the same.

However, i have noticed the above change has resulted in quite some difference in the output executable. Basically, (a.o b.o c.o) method will result in larger output size.

So what's the difference between the two methods (libx.a and individual object files)? And is there a way to work around?

The GNU binutil (for and ar ld) version i'm using is 2.16.1

Thanks.

© Stack Overflow or respective owner

Related posts about linker

Related posts about static