This is the mail archive of the
mailing list for the GCC project.
Re: Separate preprocess and compile: hack or feature?
- From: Nathan Sidwell <nathan at acm dot org>
- To: Boris Kolpackov <boris at codesynthesis dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 11 May 2017 09:48:36 -0400
- Subject: Re: Separate preprocess and compile: hack or feature?
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org>
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 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?'