Re: autoconf linking with shared object

Hi Braden, * Braden McDaniel wrote on Wed, Mar 29, 2006 at 06:18:02PM CEST: > On Wed, 2006-03-29 at 10:41 +0200, Ralf Wildenhues wrote: > > * Braden McDaniel wrote on Wed, Mar 29, 2006 at 10:32:37AM CEST: > > > [ -l* in *_LDFLAGS ] > > That's very likely because you rarely do static linking. >

Re: autoconf linking with shared object

On Wed, 2006-03-29 at 10:41 +0200, Ralf Wildenhues wrote: > Hi Braden, > > * Braden McDaniel wrote on Wed, Mar 29, 2006 at 10:32:37AM CEST: > > On Wed, 2006-03-29 at 10:02 +0200, Ralf Wildenhues wrote: > > > > > You definitely want to put dependent libraries (those `-lfoolib' flags) > > > into on

Re: autoconf linking with shared object

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hi Braden, > > * Braden McDaniel wrote on Wed, Mar 29, 2006 at 10:32:37AM CEST: >> Is this advice really still relevant? Are all those packages that apply >> -l and -L together as a unit Doing It Wrong? > > Yes. And anybody trying to link completely s

Re: autoconf linking with shared object

Hi Braden, * Braden McDaniel wrote on Wed, Mar 29, 2006 at 10:32:37AM CEST: > On Wed, 2006-03-29 at 10:02 +0200, Ralf Wildenhues wrote: > > > You definitely want to put dependent libraries (those `-lfoolib' flags) > > into one of the automake Makefile macros LIBS, someprogram_LDADD, > > libsomeli

Re: autoconf linking with shared object

On Wed, 2006-03-29 at 10:02 +0200, Ralf Wildenhues wrote: > You definitely want to put dependent libraries (those `-lfoolib' flags) > into one of the automake Makefile macros LIBS, someprogram_LDADD, > libsomelibrary_LIBADD, or similar, and not into *_LDFLAGS. I hear this advice from time to time

Re: autoconf linking with shared object

Hi Matt, * Matt Kowalczyk wrote on Wed, Mar 29, 2006 at 12:33:54AM CEST: > > I am using the gtk library and to compile it properly with automake I have > to do this: > > AM_LDFLAGS = -lcrypto -lglib-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 > -latk-1.0-lgdk_pixbuf- > 2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -

Re: autoconf linking with shared object

Thanks... I have another question. I am using the gtk library and to compile it properly with automake I have to do this: AM_LDFLAGS = -lcrypto -lglib-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0-lgdk_pixbuf- 2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0- lgmodule-2.0

Re: autoconf linking with shared object

Matt Kowalczyk wrote: > This forces me to add /usr/lib/libcrypto.so to the gcc command when I link the > object to produce an executable for instance. My gcc command looks something > like below: > > gcc --pedantic -Wall -std=c99 -O2 -g -O2 /usr/lib/libcrypto.so -o main > Main.o > my_md5.o Y

Re: autoconf linking with shared object

Hi Matt, * Matt Kowalczyk wrote on Sat, Mar 25, 2006 at 09:35:22PM CET: > One of my source files uses the library: > > #include > > This forces me to add /usr/lib/libcrypto.so to the gcc command when I link > the object to produce an executable for instance. My gcc command looks > something

autoconf linking with shared object

One of my source files uses the library: #include This forces me to add /usr/lib/libcrypto.so to the gcc command when I link the object to produce an executable for instance. My gcc command looks something like below: gcc --pedantic -Wall -std=c99 -O2 -g -O2 /usr/lib/libcrypto.so -o main