Re: variable names and `include'

2006-06-26 Thread Stepan Kasal
Hello, On Sat, Jun 24, 2006 at 02:24:09PM +0200, Tom Bachmann wrote: > a way to do this but $(eval include bar.mk), Automake is not preprocessing the whole file, so there are easier ways to fool it: NULL = $(NULL)include hoo or include = include $(include) hoo Have a nice day, Stepan

Re: variable names and `include'

2006-06-25 Thread Tom Bachmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues wrote: > One possibility to separate GNU make specific parts and portable make > parts so that Automake only sees the latter is to put those in > Makefile.am, put the GNU make specific stuff in GNUmakefile, and let the > latter 'include

Re: variable names and `include'

2006-06-25 Thread Ralf Wildenhues
Hello Tom, * Tom Bachmann wrote on Sat, Jun 24, 2006 at 02:24:09PM CEST: > > But automake complains "bad characters in variable name". I could work > around this by stopping automake from processing the file (make allows > it), but I could not find a way to do this but $(eval include bar.mk), > w

variable names and `include'

2006-06-25 Thread Tom Bachmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, [please cc me as I'm not registered to the list] I'm currently digging into how to extend automake. As make can do (nearly) everything automake can, I suppose I'll end up at a stage where everyone who wants the new stuff includes a Makefile snippe