Re: problems with $(eval include...)

2003-06-26 Thread Fabio Alemagna
On Thu, 26 Jun 2003, Ted Stern wrote: > Ah, you have autogenerated headers! Not necessarily, but it may happen. I'm working on a complete and generic build system, which understands "modules types", and on the basis of thos types it takes some actions. It uses only make and the $(eval) function t

Re: problems with $(eval include...)

2003-06-26 Thread Fabio Alemagna
On Thu, 26 Jun 2003, Ted Stern wrote: > Hi Fabio, > > Use the "-" prefix with your include statements, it's much simpler: > > -include $(DEPS) > > This will ignore the errors caused by a file not being found. > > More generally, you can make your dependency generation a lot simpler. See > Paul

Re: problems with $(eval include...)

2003-06-26 Thread Ted Stern
On 26 Jun 2003, Fabio Alemagna wrote: > My goal is to have make include .d files only when they are actually > needed, so that when make starts, it doesn't have to check whether any .c > files (from which all the .d ones are generated) have changed, so I've > come up with this solution: Hi Fabio,

problems with $(eval include...)

2003-06-26 Thread Fabio Alemagna
My goal is to have make include .d files only when they are actually needed, so that when make starts, it doesn't have to check whether any .c files (from which all the .d ones are generated) have changed, so I've come up with this solution: OBJS := ... DEPS := ... program: program-deps $(OB