Hello C programmers,
I understand the general nature of library files, that C needs them to understand include files, that they come in many flavors (.lib, .dll, .a, .so), but I don't understand the process of taking source code X and then using it to build library file Y.
My current process is this. 1) Google around until I find someone who has already build a ".a" file for the source code I'm using. 2) Copy that file to the MinGW "lib" directory. 3) Everything is great.
Since this is really pathetic, I was hoping someone could help direct me to a better process for taking source code X and then using it to build library file Y using MinGW/GCC. I'm sure this is a really basic issue, but all the information I can find on C libraries usually looks like
ar rc libutil.a util_file.o util_net.o util_math.o and involves using ".o" object files (which never come with source code) and it never explains the missing links between the source code and the library file.