Re: why removing configure substitutions for myprog_DEPENDENCIES?

2005-04-20 Thread Stepan Kasal
Hello, On Tue, Apr 19, 2005 at 04:10:06PM +0200, Harald Dunkel wrote: > Would it be possible to compute myprog_DEPENDENCIES at make's > runtime instead? At that time the real set of library names is > known, even for 'make MYLIB=liba.a'. Maybe something like > > myprog_DEPENDENCIES = $(patsubst -

Re: why removing configure substitutions for myprog_DEPENDENCIES?

2005-04-19 Thread Harald Dunkel
Stepan Kasal wrote: > Hello, > > On Tue, Apr 19, 2005 at 02:50:03PM +0200, Harald Dunkel wrote: > >>Why are the configure substitutions removed? > > > because they are not known at the time when automake runs. > Understood. Would it be possible to compute myprog_DEPENDENCIES at make's runtime

Re: why removing configure substitutions for myprog_DEPENDENCIES?

2005-04-19 Thread Stepan Kasal
Hello, On Tue, Apr 19, 2005 at 02:50:03PM +0200, Harald Dunkel wrote: > Why are the configure substitutions removed? because they are not known at the time when automake runs. Automake wtites Makefile.in, which is tehn distributed. It cannot know what will be the result of ./configure on the hos

why removing configure substitutions for myprog_DEPENDENCIES?

2005-04-19 Thread Harald Dunkel
Hi folks, I have a question about how the *_DEPENDENCIES are computed from *_LDADD: If I write a Makefile.am bin_PROGRAMS = myprog MYLIB = liba.a myprog_LDADD = \ $(MYLIB) \ libb.a \ -Lsomepath \ -lother the