>> Don't know about others, but the reason why I don't use c-macro-expand is
>> because it basically can't work right without parsing my Makefile(s) to know
>> which include dirs should be used. And since it doesn't do that, I've found
>> it of little use.
> OK. I see now. For Emacs, the source seems to have the same flags. So, in
> that case, I guess you could do something like:
> (setq c-macro-cppflags "-Demacs -DHAVE_CONFIG_H -DUSE_LUCID -I.
> -I/home/nick/emacs/src -D_BSD_SOURCE -I/usr/X11R6/include")
Except that Emacs is not the only project I work on that uses the
C language.
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
