.lib files are “libraries” and contain “collections” of compiled code that says so. Thus, this is a way to provide software components without issuing, for example, internal source code. They can be generated as “output” from the “assembly”, as well as executable files.
The specific content depends on your platform / development environment, but they will contain characters for the linker to “plug in” the function calls provided, for example. library header file.
Some libraries are "dynamic" (.DLL on Windows), which means that the "interception" of function calls is configured when loading an executable file using a library, which allows you to change the library implementation without restoring the executable file.
Last thing. You say you are learning C ++, and the common confusing point is that the “characters” generated by the C ++ compilers are “distorted” (in order to allow, for example, function overloading), and this “manipulation” is not it is standardized for different compilers, therefore libraries often resort to C for the "API" library (like OpenGL), although the library can be implemented in C ++ internally.
Hope to shed light on .lib files. Happy OpenGL coding :-)
source share