Difference between Header file and Library
Header Files: The files that tell the compiler how to call some functionality (without knowing how the functionality actually works) are called header files. They contain the function prototypes. They also contain Data types and constants used with the libraries. We use #include to use these header files in programs. These files end with .h extension.
Library: Library is the place where the actual functionality is implemented i.e. they contain function body. Libraries have mainly two categories :
Static: Static libraries contains object code linked with an end user application and then they become the part of the executable. These libraries are specifically used at compile time which means the library should be present in correct location when user wants to compile his/her C or C++ program. In windows they end with .lib extension and with .a for MacOS.
Shared or Dynamic: These libraries are only required at run-time i.e, user can compile his/her code without using these libraries. In short these libraries are linked against at compile time to resolve undefined references and then its distributed to the application so that the application can load it at run time. For example, when we open our game folders we can find many .dll(dynamic link libraries) files. As these libraries can be shared by multiple programs, they are also called as shared libraries.These files end with .dll or .lib extensions. In windows they end with .dll extension.
Example : Math.h is a header file which includes the prototype for function calls like sqrt(), pow() etc, whereas libm.lib, libmmd.lib, libmmd.dll are some of the math libraries. In simple terms a header file is like a visiting card and libraries are like a real person, so we use visiting card(Header file) to reach to the actual person(Library).
Let’s see the difference between these two in tabular form,so that it can be easily comparable:
|They have the extension .h
||They have the extension .lib
|They contain function declaration and even macros.
||They contain function definitions
|They are available inside “include sub directory” which itself is in Turbo compiler.
||They are available inside “lib sub directory” which itself is in Turbo compiler.
|Header files are human-readable. Since they are in the form of source code.
||Library files are non-human-readable. Since they are in the form of machine code.
|Header files in our program are included by using a command #include which is internally handle by pre-processor.
||Library files in our program are included in last stage by special software called as linker.
Whether you're preparing for your first job interview or aiming to upskill in this ever-evolving tech landscape, GeeksforGeeks Courses
are your key to success. We provide top-quality content at affordable prices, all geared towards accelerating your growth in a time-bound manner. Join the millions we've already empowered, and we're here to do the same for you. Don't miss out - check it out now!