Re: How to tell libtool to have/work with one of [.lo|.o] file ( ifpossible )

2003-02-06 Thread Jeff Dubrule
On Wed, Feb 05, 2003 at 05:09:14PM -0600, Bob Friesenhahn wrote: > Unfortunately, there is a design problem with libtool. There should > be libtool command-line switches to support this, but instead these > options must be set when libtool is configured. These options are set > via an autoconf co

Re: How to tell libtool to have/work with one of [.lo|.o] file ( ifpossible )

2003-02-05 Thread Bob Friesenhahn
On Wed, 5 Feb 2003, Praveen Jain wrote: > >> > >> The main motivation is to reduce the build time > >> approximately by a factor of 2 which would be a > >> tremendous help for us. > > > >--disable-shared or --disable-static. If you want static and shared, > >you don't have a choice. > > Where do yo

Re: How to tell libtool to have/work with one of [.lo|.o] file ( ifpossible )

2003-02-05 Thread Albert Chin
On Wed, Feb 05, 2003 at 02:11:39PM -0800, Asim Suter wrote: > I see that libtool compiles every C source file two times > 1) once to generate ".lo" files > 2) second time to generate ".o" files > > Is it possible to "tell" libtool to generate > only one type of object file ? My belief is that >

How to tell libtool to have/work with one of [.lo|.o] file ( ifpossible )

2003-02-05 Thread Asim Suter
Hello, We build shared libraries and executables on a Linux system for Pentium processor. We use libtool along with automake and autoconf as part of our build infrastructure. I see that libtool compiles every C source file two times 1) once to generate ".lo" files 2) second time to generate "