Re: I can do it in Makefile.in but not sure how to translate it to Makefile.am

2006-11-16 Thread J.H.
Actually from my last e-mail it got me thinking concerning the outside program doing something to the make file - I found it and I seem to have fixed the problem. There's a perl script that gets run just after automake is finished that generated the line I was worried about. I've been able to

Re: I can do it in Makefile.in but not sure how to translate it to Makefile.am

2006-11-16 Thread J.H.
Ralf Wildenhues wrote: Hello John, * J.H. wrote on Thu, Nov 16, 2006 at 03:32:14AM CET: kcookieserver_skel.cpp: kcookieserver.kidl $(DCOPIDL2CPP) --c++-suffix cpp --no-signals --no-stub kcookieserver.kidl foobar While this works great in the Makefile.in, when Makefile.in gets

Re: I can do it in Makefile.in but not sure how to translate it to Makefile.am

2006-11-16 Thread Ralf Wildenhues
Hello John, * J.H. wrote on Thu, Nov 16, 2006 at 03:32:14AM CET: > > kcookieserver_skel.cpp: kcookieserver.kidl > $(DCOPIDL2CPP) --c++-suffix cpp --no-signals --no-stub > kcookieserver.kidl > foobar > > While this works great in the Makefile.in, when Makefile.in gets rebuilt > fr

Re: How to properly define package-wide flags.

2006-11-16 Thread Ralf Wildenhues
Hello Benoit, * Benoit Sigoure wrote on Thu, Nov 16, 2006 at 08:03:57AM CET: > > Akim's idea of AM_*FLAGS is that they are not meant to be defined in > configure.ac but in Makefile.ams. His approach is to AC_SUBST([MY_*FLAGS], > [-package-wide-flags]) and then have a common.mk (say at top-level)