> > ifndef CRYSTAL 
> >    error "no CRYSTAL defined in your Makefile"
> > endif
> 
> Maybe make that
>   $(error no CRYSTAL defined in your Makefile)

maybe? maybe? that is *exactly* what I was looking for!

now I'll re-check the documentation to see why I missed this one.

> (Did you see my previous message about the $(error message) function?)

obviously not...

> > That seems to be my only option so far, but that requires that makes
> > interprets the whole Makefile, because rule-execution 
> starts only after
> > full interpretation.
> 
> Right. What is so bad about it?

I'd hate to make sure the rest of the Makefile would not contain syntax
errors. Just something I can think of right now: I use the values the
user has provided ao. for constructing file names, if the usered
specified a two-word value where I except a one word value interesting
error messages could result.

> Just a thought: .inc is way too overloaded IMO

I think I'll follow that suggestion

> And I don't think you can 
> instruct make to
> execute any commands outside of a rule.

true, but that $(error xxx) can be outside a rule!

> So you probably want a target like
> 
> checkSetup:
> 	ifndef CRYSTAL 
> 		$(error no CRYSTAL defined in your Makefile)
> 	endif

no need for the target :) :)

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist