I have a newbie's C module development question: I have a closed-source C API that I want to use from AOLserver. Ok, no problem, creating a myfoo.so AOLserver loadable module to do that should be straightforward. Unfortunately, the vendor of this closed-source API ships only the non-shared libfoo.a version of their library - they don't ship a libfoo.so.
Now, I should be able to just re-compile all of AOLServer with libfoo.a linked in, right? I think the place to do that is in aolserver/nsd/Makefile, but I'm still a bit vague on basics like that... Are there any particular examples of static linking in the AOLserver code that I should look at? Also, I'm thinking that if I link libfoo.a statically into my nsd8x binary, I can still create myfoo.so as a loadable module - there's no reason I need to also link it statically, right? Finally, it would be nice to avoid having to statically link libfoo.a into nsd8x in the first place. Is it somehow possible to link libfoo.a into my myfoo.so, rather than nsd8x? I don't think so, but I'm not really sure. Thanks for any advice! -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com
