Thank you Lyle for clearing things up. =) I'll take a look at .la stuff. Thanks everyone for pointing me in the right direction. /Bo ----- Original Message ----- From: <lrtaylor@xxxxxxxxxx> To: <bodo@xxxxxxxx>; <gcc-help@xxxxxxxxxxx> Sent: Tuesday, November 18, 2003 7:20 PM Subject: RE: How handle static libraries? Bo, Basically, the common way to do it is the way you're doing it. If C uses A and you use C, you link to both C and A (in that order). Something you might look at, however, is .la files (usually created by libtool, I believe). These are information files that the compiler/linker can use to know how to use a given library. It may also be able to tell the compiler what libraries your library depends on so that it can link them in automatically. Now, I'm not very familiar with these files and how they work, but it might be something you would want to look into. You may find your answer there. Good luck, Lyle -----Original Message----- From: gcc-help-owner@xxxxxxxxxxx [mailto:gcc-help-owner@xxxxxxxxxxx] On Behalf Of Bo Do My question in this post is actually: What is the common way to handle/create static libraries which uses other libraries? Thanks for reading this post. Don't know if it makes sense! =) /Bo
