Re: Automatic dependecy based compilation targets

* Dizzy wrote on Wed, Jan 31, 2007 at 12:44:39PM CET: > I would like to somehow describe a Makefile.am file as: > > libsocket_a_SOURCES=Socket.cpp Socket.hpp > > libconnection_a_SOURCES=Connection.cpp Connection.hpp > libconnection_a_LIBADD=libsocket.a > > And then, if I have a sbin_PROGRAMS lik

Re: What variable contains the library path?

On Wed, 2007-01-31 at 05:48 -0500, Jim wrote: > From the automake document, I'd infer that the following would work, > but it doesn't. You'd better read once more ;) > cgi_libdir=$(libdir)/cgi-bin > cgi_libdir_SCRIPTS = confdata/index.cgi > > Makefile.am:18: `cgi_libdir_SCRIPTS' is used but `cg

What variable contains the library path?

From the automake document, I'd infer that the following would work, but it doesn't. cgi_libdir=$(libdir)/cgi-bin cgi_libdir_SCRIPTS = confdata/index.cgi Makefile.am:18: `cgi_libdir_SCRIPTS' is used but `cgi_libdirdir' is undefined make: *** [Makefile.in] Error 1 So how would I accomplish pu

Automatic dependecy based compilation targets

Hi there I would like to somehow describe a Makefile.am file as: libsocket_a_SOURCES=Socket.cpp Socket.hpp libconnection_a_SOURCES=Connection.cpp Connection.hpp libconnection_a_LIBADD=libsocket.a And then, if I have a sbin_PROGRAMS like sbin_PROGRAMS=prog1 prog1_SOURCES=... prog1_LDADD=libconn