lightlu
asked on
shared library downsize by libraryopt on sourceforge.net
How to use libraryopt to downsize shared library, uClibc, with respect to embedded target file system. thanks
http://sourceforge.net/projects/libraryopt
http://sourceforge.net/projects/libraryopt
ASKER
Is there a step by step example? I give a very simple dynamic shared library named liball.so which composed of lib1.o and lib2.o, with a program which uses function belongs to lib1.o only. I create path, index and build file according to document in target/usr/lib/optinfo/lib all, but the result of libopt is null. thanks very much.
What was the command line you used ?
Are you sure that functions in lib1.o do not call functions in lib2.o ... Also make sure that there are no other programs in the directory which use lib2.o, directly or indirectly
Are you sure that functions in lib1.o do not call functions in lib2.o ... Also make sure that there are no other programs in the directory which use lib2.o, directly or indirectly
ASKER
Sorry, I had tried it out. And I think the difficulity to use libraryopt is to prepare the build script for it. While deling with embedded system, the cross toolchain envirement increase the usage complexity. Is there any image downsize real case? What is the downsize percentage? Thanks
> Is there any image downsize real case? What is the downsize percentage?
I have not tried it or any other tool for downsizing
use strip(1) to remove the symbols. The strip(1) command gives you a good deal of control over what symbols to eliminate; see its documentation for details.
I have not tried it or any other tool for downsizing
use strip(1) to remove the symbols. The strip(1) command gives you a good deal of control over what symbols to eliminate; see its documentation for details.
ASKER
Yes, strip is good tool for retrieve binary symbol information. But only the raw strip usage to deliver commercial product is not realistic. The minimun object for libraryopt for downsizing shared library is *.o file. However uclibc.so is built from libc.a which composed of those *.o choosen from menuconfig. I am trying give a build script which build libuclibc.so from all *.o directly.
Does your index file contain the entries you expect?
What does your build file look like?
What platform are you building for?
What toolchain are you using?
Post these and I'll try to help.
What does your build file look like?
What platform are you building for?
What toolchain are you using?
Post these and I'll try to help.
ASKER
I found that I failed to optimize my simplest example on i386 platform. This example includes lib1.c, lib2.c and go.c as following.
lib1.c: show1() {printf("this is show1\n");}
lib2.c: show2() {printf("this is show2\n");}
go.c: main() { show1(); }
The output of libindex only contains two lines, O lib1.o and O lib2.o, which was produced from the shell command "libindex liball.so -o lib1.o lib2.o > index". The liball.so is composed of lib1.o and lib2.o.
I doubt the correctness of index file although I have no experience of libraryopt before. In other hand, I traced into libopt and found that it did not include lib1.o while process the undefined symbol show1 of go. So the optimized liball.so even does not have show1 function in it(I use nm to list its symbols). Could you help to answer it? Thanks
light
lib1.c: show1() {printf("this is show1\n");}
lib2.c: show2() {printf("this is show2\n");}
go.c: main() { show1(); }
The output of libindex only contains two lines, O lib1.o and O lib2.o, which was produced from the shell command "libindex liball.so -o lib1.o lib2.o > index". The liball.so is composed of lib1.o and lib2.o.
I doubt the correctness of index file although I have no experience of libraryopt before. In other hand, I traced into libopt and found that it did not include lib1.o while process the undefined symbol show1 of go. So the optimized liball.so even does not have show1 function in it(I use nm to list its symbols). Could you help to answer it? Thanks
light
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
libopt [-s] [ -d <destroot> ] <targetroot>
<targetroot> should be the base directory of the full target filesystem tree. It must include all the executable programs and shared libraries that will be present on the target.
The optional <destroot> specifies an alternate directory where the optimized libraries will be placed. If <destroot> is not specified, <targetroot> will be used as the destination, overwriting the original target libraries.
The optional argument "-s" should be specified if the optimized libraries should be stripped. This can greatly reduce the size of the optimized libraries, but reduces the amount of debugging information available.
http://libraryopt.sourceforge.net/use.html
Configuring the Library Optimizer Tool
http://libraryopt.sourceforge.net/config.html