Re: Using libtool for linking

2007-08-20 Thread Benoit SIGOURE
On Aug 17, 2007, at 8:42 PM, Jason Curl wrote: Peter O'Gorman wrote: On Fri, 2007-08-17 at 13:29 +0200, Jason Curl wrote: As for testing the situation, AC_CHECK_LIB makes me believe it will work. But it only works in a subset of cases (i.e. static only). I have another implementation that

Re: Libtool woes

2007-08-20 Thread Ralf Wildenhues
Hello Jason, Brian, all, * Jason Curl wrote on Mon, Aug 20, 2007 at 11:41:03AM CEST: > Brian Dessent wrote: >> [ snip nice, concise and well-written explanations ] >> > Brian - thanks for the concise description. Ralf - any way to may be > add an addendum to the libtool docs for this, just for inf

Re: Creating ONLY static libraries

2007-08-20 Thread Mike Frysinger
On Monday 20 August 2007, Omri Azencot wrote: > Hello > I am using libtool 1.5.23 during the building process, I am also using > autoconf(2.61) to create the configure file. > in configure.ac I used the macro AC_DISABLE_SHARED, and in the log I got > the following line: > > checking whether to buil

Creating ONLY static libraries

2007-08-20 Thread Omri Azencot
Hello I am using libtool 1.5.23 during the building process, I am also using autoconf(2.61) to create the configure file. in configure.ac I used the macro AC_DISABLE_SHARED, and in the log I got the following line: checking whether to build shared libraries... no but, after "make install" the pa

Re: Libtool woes

2007-08-20 Thread Jason Curl
Brian Dessent wrote: .dll.a is the import library. .dll is the actual library. Both should be produced. The import library is used when linking against the library, but it is not needed at runtime and contains no code. It's typically distributed in the same context as headers -- it is needed