One or many libraries?
-
Hi, Time ago I began to create some static libraries of functions/classes in that I frequently use in my apps. Classes that uses MFC stuff is in one library and the rest of the stuff classified in another five. I "think" (please confirm) that having multiple library files make manteniance and changes compiling faster. Also I "believe" that Visual Studio compiler will be smart enough to NOT include all the object files of classes I don't use in my final executable. The question, including my 2 "thinks" above, is: "using separate library files has a real benefit?" Thanks, Mauro.
-
Hi, Time ago I began to create some static libraries of functions/classes in that I frequently use in my apps. Classes that uses MFC stuff is in one library and the rest of the stuff classified in another five. I "think" (please confirm) that having multiple library files make manteniance and changes compiling faster. Also I "believe" that Visual Studio compiler will be smart enough to NOT include all the object files of classes I don't use in my final executable. The question, including my 2 "thinks" above, is: "using separate library files has a real benefit?" Thanks, Mauro.
You are correct on both counts. I would also suggest you convert the static libraries into dynamic libraries 'cause then you have a lot more options of either linking it implicitly or explicitly or even delay loading the DLL.
«_Superman_» I love work. It gives me something to do between weekends.
-
You are correct on both counts. I would also suggest you convert the static libraries into dynamic libraries 'cause then you have a lot more options of either linking it implicitly or explicitly or even delay loading the DLL.
«_Superman_» I love work. It gives me something to do between weekends.
Yes. I was thinking in turning some libraries into dlls. I'm not friend of having an app of one .exe and lots of .dll, but sometimes there aren't other options. Best regards, Mauro.