9 Jan
2013
9 Jan
'13
18:27
On Wed, Jan 9, 2013 at 11:53 PM, Jason Felice jason.m.felice@gmail.comwrote:
Does anyone have a solution for the clang compile time issue?
I spent an hour in the clang source looking for a way to turn off its crazy-sophisticated tracking of macro expansion, which is my theory about why gambit code takes so long to compile. There's some kind of internal flags for this, but I don't know how to get it through the driver. I was wondering if anyone else has figured this out.
How about running the source through cpp before passing to clang?
--
Alex