ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
I am having a library named toolkit.a.
Its contains some exported functions.
I am using only one function from that library, which must be very small in size.
e.g. tk_strlen.
Problem is that my execuable size increases a lot.
Though I am using only one function from that library, I think my executable gets
bundled with all the functions.
How should I notiify the linker to ignore all the unused functions from the final build?
Did you write toolkit.c yourself?
If so (or even when not) you could try to just take out (copy) the code into your program (if the license allows, and you give credits where due).
If you did not write toolkit.c yourself then realize that though you only use one function, that function may use a lot of other functions in the same library...
Back to square one,
This library is a part of our project, and writen by us.
Problem was that our project contains a set of .so files.
We separated a common set of function from all the libraries,
and maintained it in toolkit.a.
Our project specification does not want a introduction of new .so file.
But using toolkit.a resulted in increased size of the libraries.
There must be some way/option to avoid bundling of non used function
in a final build.
Praj.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.