Why there is include folder with libraries in open source libraries

Question

0.00/5 (No votes)

See more:

Hi,
I am using ICU binary as an external binary.I have lib/dll and an include folder having some ".h" files.
Why there is include folder with libraries in open source libraries?

Posted 22-May-12 21:56pm

ahsanriaz1K

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

E.F. Nijboer · Accepted Answer · 2012-05-22T22:15:00

Not totally clear what you mean, but my guess is that you mix-up some things. The dll is used to include in your project and is already compiled so the compiler won't need to do this over and over again. The .h files contain certain datatypes used in the library dll. The dll might expect some kind of struct type as input for some functions. The header files contain those specific types so you don't need to figure them out and redefine yourself.
In some crude way you can look at header files as some kind of spoiler alert for the compiler that tells it what to expect in the code files. It also gives you information about defined types and function.

Ps. also libraries that aren't open source can include the header files. They don't contain the actual implementation (or at least shouldn't) but do make the library usable.

Good luck!

CPallini · Accepted Answer · 2012-05-22T22:06:00

Solution 1

There should be an include folder (or, at least, an include file) in all libraries, since the library client program (that is your application) needs at least the prototypes of the library exported functions.

Posted 22-May-12 22:06pm

CPallini

v2

Comments

ahsanriaz1K 23-May-12 5:08am

You wrote "needs at least the prototypes of the library exported functions" but why? Can you please tell me?

CPallini 23-May-12 5:30am

How can you (actually the compiler) tell you're correctly calling a function without knowing its prototype?

Sandeep Mewara · Accepted Answer · 2012-05-22T22:10:00

Why there is include folder with libraries in open source libraries?
If I understand your question, it asks why do we have few *.h files in a folder.

This is because, this folder will have all the libraries that the open source is referring/using at some point. Keeping it separate in a folder makes it easy to find the external dependent libraries from maintenance point too. Separate folder signifies the folder as referenced library folder.

Why there is include folder with libraries in open source libraries

3 solutions

Solution 3

Solution 1

Solution 2

Add your solution here

Preview 0