Hi Ralph, On Friday 29 August 2003 16:53, Schleicher Ralph (LLI) wrote: > In libtool jargon, ".so file" is a synonym for a shared library. > This includes all companion files, but their names and number > depend on libtool's configuration and build options. E.g., HP-UX > uses .sl instead of .so for the shared library file name extension, > but libtool users on HP-UX also talk about .so files, so that > libtool users on other systems don't get confused.
That's my point. My understanding of Stephen problem is that he doesn't want to build/install the companion files. On Wednesday 27 August 2003 16:21, Stephen Torri wrote: > I am trying to build libraries that will act as modules in a program. At > present when I do a compile its building .la, .so, .so.0.0 and .so.0.0.0 > files. I am looking for advice on how to setup my Makefile.am file so > that all I get installed is a .so file. Ideas? So in his situation, patching libtool and using -shared isn't really going to solve his problem. Correct? Cheers, -- Tom Howard _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool