There are static libraries (LIB) and dynamic libraries (DLL) - but note that .LIB files can be either static libraries (containing object files) or import libraries (containing symbols to allow the linker to link to a DLL). Libraries are used because you may have code that you want to use in many programs. For example if you write a function that counts the number of characters in a string ...
A lib file is just a collection of related obj files, much like putting obj files in a directory. That is essentially what a lib file is, a library of obj files.
On Windows, there are .lib files, which are quite the same thing, but for Windows instead of Unix. An additional subtlety is that in order to link some code against a DLL (on Windows), you have to link against a .lib file which contains simple wrappers which invoke the DLL.
Files in /lib and /usr/lib are supposed to be mostly read only and identical between systems. (If it was a container image, they could be fully read only and shared between systems; on a stand alone system, they need to be writable to install updates.) Files in /var are specific to the local system and frequently contain data that is generated by system operation. Typically distribution ...
I have a binary file - Windows static library (*.lib). Is there a simple way to find out names of the functions and their interface from that library ? Something similar to emfar and elfdump utili...
My 64 bit Ubuntu 13.04 system has the following directories in /: lib lib32 lib64 libx32 libexec In the /usr directory there is: lib lib32 libx32 libexec This seemed like something that could be ...
Download ta-lib-0.4.0-msvc.zip and unzip to C:\ta-lib. This is a 32-bit binary release. If you want to use 64-bit Python, you will need to build a 64-bit version of the library. Some unofficial (and unsupported) instructions for building on 64-bit Windows 10, here for reference: Download and Unzip ta-lib-0.4.0-msvc.zip
If the .lib is a "real" lib with the actual code (I've never used DLLs save for the system-provided ones, but I believe you make 'import libs' for your own DLLs), then the DLL isn't required. As for the subject, #pragma comment (lib,xxx) allows programs to add certain options for the linker.
The LIB must be output in a directory where the client projects can find it. There a number of ways of going about this, such as explicitly including the base project DLLs output path in the client projects linker input path. I prefer to set all projects to use a common output directly, so I set all projects to the following:
.lib is the extension used for static library on Windows, and according to wikipedia, is also used as "import library" under windows, so I strongly suspect they're just another name for what the binutils call .a files.
