Separate preprocess and compile: hack or feature?
Nathan Sidwell
nathan@acm.org
Thu May 11 13:48:00 GMT 2017
Hi Boris
> In the build system I am working on we are looking at always performing
> the preprocessing and then C/C++ compilation as two separate gcc/g++
> invocations. The main reason is support for distributed compilation but
> see here[1] for other reasons.
How c++ modules fit into a build system is currently an open question.
Richard Smith & I have talked about it, but with no firm conclusion.
However, I think that breaking out the preprocessor is not the right
answer. We were leaning more to some kind of hook in the compiler to
answer 'I can't find module FOO, where is it?'
nathan
--
Nathan Sidwell
More information about the Gcc
mailing list