Ames, Andreas (Andreas) wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Stefan Seefeld Sent: Monday, August 06, 2007 12:33 PM Subject: Re: [boost] Release Tools Analysis Part I: Build systems
That's not quite correct. That interface you are talking about isn't quite enough to let you plug in external scanners, since a real preprocessor such as boost.wave would need to interact with other tools to fetch preprocessor flags such as include search paths, predefined macros, and the like, without which it would fall over rather quickly.
I have done it for IDL-preprocessing. You always have the build environment at your disposal to communicate the items you have mentioned. I don't claim it is perfect, but it is sth. to build upon, IMHO.
For most C/C++ code you need system search paths, which depend on the compiler actually used. Finding user-provided headers isn't enough. Regards, Stefan -- ...ich hab' noch einen Koffer in Berlin...