larocque@jupiter.crd.ge.com (David M. LaRocque) (04/10/90)
*************************************** The massive size of my current C project has me looking for alternate means of managing it. I have never created my own libraries before, but I was thinking that it may help organize things. I read through the ar and lorder man pages and could probably create my own libraries, but my question is even more fundamental. Are libraries only useful for those routines that are used by many different projects, or do they offer benefits even if they contain project-specific functions. When does one decided that a library is appropriate? Is there any advantage over simply separating the code into object modules? -Dave LaRocque larocque@crd.ge.com ******************************************
kla@physc1.byu.edu (04/11/90)
My understanding of libraries under unix is somewhat limited, but I haven't seen any advantage to using libraries there. However, with MSC 5.1 I understand that libraries are very useful because they only link in the actual libraries needed by a particular program. Under unix it seems that everything is linked in every time. If I am wrong about this I'd like to know about it.
dkim@wam.umd.edu (Daeshik Kim) (04/12/90)
Is MSC lib a shared lib? As a runtime lib, I guess there'll be no difference using only those you need or the whole lib for runtime. Only difference I can think of is complile time. -- Daeshik Kim H: (301) 445-0475/2147 O: (703) 689-5878 SCHOOL: dkim@wam.umd.edu, dskim@eng.umd.edu, mz518@umd5.umd.edu WORK: dkim@daffy.uu.net (uunet!daffy!dkim)