Hello,

I am a novice Linux user. I have a question.

I have prepared a static lib(.a) comprising 2 function definitions. I have created a different shared library(.so) comprising 2 more functions. The two functions of .so use the functions defined in the .a file. That is, the .so file uses the services of the .a file.

Next, I create an executable that uses the shared library(.so). When I build my executable, it needs to be linked with the .a file as well. Otherwise it gives me undefined reference for the functions defined in the .a file. Why is that so? I am posing this question because, the .a file has already been included(static linking) while bulding the .so.

Is there any workaround so that I need not link the .a file with my final executable?

Thank you,
AD

What are the commands you use to create the static library and the shared library?

If the static library has been specified when creating the shared library, then there is no need to include the static library in your main program, except when you use the static library directly.

1 members found this post helpful.

Well Thanks for your input. I found out that the order of the lib matters. Again it is good to add start_group and end_group for the archives in order to resolve the cyclic dependency.

Thank you,
AD