linux 平台静态库的合并方法(解决多个静态库间相互依赖的问题)


How to merge two “ar” static libraries into one?

原文链接 

https://stackoverflow.com/questions/3821916/how-to-merge-two-ar-static-libraries-into-one

Asked 10 years, 4 months ago
Viewed 84k times
 
93

I have 2 static Linux libraries, created by ar crlibabc.a and libxyz.a.
I want to merge them into one static library libaz.a.
How can I do this.

I want to create a merged static library, not to give both libraries to final link of applications.

6 Answers

62
 

You can extract the object from both the .a files and create your .a file using the extracted .os:

ar -x libabc.a
ar -x libxyz.a
ar -c libaz.a  *.o
  • 66
    Danger, Will Robinson! This works only if the names of the members in libabc.a and libxyz.a don't overlap. Otherwise you'll overwrite one and it'll be lost. – David Given Jun 7 '13 at 15:45
  • 7
    Moreover, libabc.a may contain objects having the same name (originated form different directories) -- re-assembling won't work then! – Igor R. May 25 '14 at 8:18
  • 18
    ar -c didn't work for me (Ubuntu 14.04). I got ar: no operation specified. I did ar -qcinstead and that worked well. – Max Dec 31 '14 at 15:02
  •  
    ar t lib.a can be used for view the files in library without actually extracting the files. – raj_gt1 May 11 '15 at 14:56
  •  
    how can I do that in automake ? – shuva May 29 '16 at 20:34 
 
126

There are at least three ways to do this natively. The first and most portable way is to use libtool. After having built the other libraries also with libtool, you can combine them just by adding the .la libs to an automake libaz_la_LIBADD variable, or directly from a Makefile with something like:

libtool --mode=link cc -static -o libaz.la libabc.la libxyz.la

The other two are at least available when using GNU ar. You can use an MRI script (named for example libaz.mri), such as:

create libaz.a
addlib libabc.a
addlib libxyz.a
save
end

and then execute ar as:

ar -M <libaz.mri

Or you can use a thin archive (option -T), which will allow adding other archives without getting them nested inside, although the downside is that if you want to distribute the static library, the detached object will be missing:

ar -rcT libaz.a libabc.a libxyz.a

All the above methods gracefully handle overlapping member names from the original archives.

Otherwise, you'd have to unpack into different directories and repack again, to avoid replacing overlapping member names:

mkdir abc; cd abc; ar -x ../libabc.a
mkdir xyz; cd xyz; ar -x ../libxyz.a
ar -qc libaz.a abc xyz
  • 19
    For those that want a normal archive (not thin), one simple thing that can be done is create a thin archive, then convert it to a normal archive. Something like: ar cqT libaz.a libabc.a libxyz.a && echo -e 'create libaz.a\naddlib libaz.a\nsave\nend' | ar -M. This creates a temporary thin libaz.a, and then converts the thin archive into a normal one (so you can move/distribute it). This also gracefully handles when your library names have special characters (spaced, pluses, or commas) (i.e. ar cqT libbundle.a libfoo++.a 'libbar baz.a'). But +1 from me!– Cornstalks May 28 '14 at 22:58 
  •  
    What is the downside to the first MRI script example given? – j b Nov 13 '14 at 13:06
  •  
    Nice answer! Good to see some options that don't require you extracting and re-achiving. Also i think @Cornstalks idea is good. Maybe should be added to the answer? – Lightbulb1 Apr 2 '15 at 14:12 
  •  
    Hey when I try to use the command for libtool I get these erros: libtool: link: unable to infer tagged configuration libtool: error: specify a tag with '--tag' Any ideas how to fix that ? – Lars Nielsen Jan 11 '19 at 9:54
  •  
    @Guillem @Cornstalks Great answer. What if the --Wl,-whole-archive option is required in original linking command for multiple lib*.a, and I need to combine all lib*.a into one.a. When linking again, --Wl,-whole-archive won't work with one.a. What is your suggestion? stackoverflow.com/questions/56323197/… – thinkdeep May 28 '19 at 2:28
10

If you simply do it as :

ar x a.a
ar x b.a
ar c c.a  *.o 

you will lost some object files if there are members with same name in both a.a and b.a so, you need to extract members of different archives into different folder:

ar x a.a && mv *.o a_objs
ar x b.a && mv *.o b_objs
ar c c.a a_objs/*.o b_objs/*.o

further more, it is posible that there are multiple members of same name in one archive (say in a.a), if you run ar x a.a, you will get only one for those members of same name.

The only way to extract all members of same name in one archive is to specify the member number by option 'N':

ar xN 1 a.a  xxx.c.o && mv xxx.c.o xxx.c.1.o
ar xN 2 b.a  xxx.c.o && mv xxx.c.o xxx.c.2.o
...

this would be a tedious work, so you will have to write a more sophisticate script to do that job.

One optional solutions is that you can combine multiple archives into one shared library:

g++ -shared -o c.so -Wl,--whole-archive a.a b.a 

this way the linker will handle all things for you!

  • 1
    Samuel, thank you. But in combining into shared library, all object should be compiled with -fPIC. – osgx May 9 '14 at 16:06
 
0

Even better you perform partial linking on each library and them make an archive of the two resulting object files. That way it operates like shared libraries would

You do partial linking with 

gcc -r --nostdlib

so either instead of making the intermediate archive or after reextracting it, run

gcc -r --nostdlib $CFLAGS $OBJECTS_A -o $LIBNAME_A.o
gcc -r --nostdlib $CFLAGS $OBJECTS_B -o $LIBNAME_B.o

then

ar -cr $LIBNAME_JOINED.a $LIBNAME_A.o $LIBNAME_B.o
  •  
    It's not really answering question asked - as he asked for libraries. Many times you don't even have sources for libraries given, or want to keep them prebuilt from other reasons. – pholat May 5 '19 at 7:01
0
ar -x libx264.a
mkdir sub && cd sub
ar -m ../libx264.a `ar -t ../libx264.a |sort|uniq|grep "\.o"`
ar -x ../libx264.a

now you have two version of "macroblock-10.o"

0
ar crsT libaz.a libabc.a libxyz.a

Here, you create archive of archives and then 'flatten' (thinning) result with T flag. Not sure how it'll work with same name .o files that might be contained within.


免责声明!

本站转载的文章为个人学习借鉴使用,本站对版权不负任何法律责任。如果侵犯了您的隐私权益,请联系本站邮箱yoyou2525@163.com删除。



 
粤ICP备18138465号  © 2018-2025 CODEPRJ.COM