I have a static library that I want to distribute that has includes Foo.c/h and someone picks it up and includes my static library in their application.
Say they also have Foo.c/h in their application. Will they have linking errors?
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 static library that I want to distribute that has includes Foo.c/h and someone picks it up and includes my static library in their application.
Say they also have Foo.c/h in their application. Will they have linking errors?
The name of a source file is not significant in the linking process.
If the file has the same contents, then you’ll have a problem, assuming that the .c file contains exported symbols (e.g. non-static or non-template functions, or extern variables).