I have a project which I can exclude some of libraries from linker and still builds ?
Is it any better to exclude them in terms of the performance and memory of final product ?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a project which I can exclude some of libraries from linker and still builds ?
Is it any better to exclude them in terms of the performance and memory of final product ?
Excluding some unused libraries from the final executable might make startup a bit faster and save a tiny amount of memory – chances are only the header and library startup code will actually end up being loaded, and these can be paged out after startup.
However, don’t do it manually. If you were told to add the library there’s probably a reason for it – perhaps some function call you’re not using yet requires it, and later on if you use that function call you may have forgotten about it.
Most linkers have an option to exclude unused libraries automatically, so you may want to just enable that option to have it take care of things for you.
Note: In some rare cases, the library’s startup code might have some important effect, in which case you should not exclude it. This is something that is best determined by checking the library’s documentation; things like this should (hopefully!) be clearly documented.