Boost logo

Boost-Build :

From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2006-04-19 19:32:40


> I could also provide a rule to test a single header file that would
> forgo all the extra cruft.

I think this would be best. If someone needs to walk a directory tree
recursively, it is best to decouple that logic from what is done with each
file. And if this avoids having to generate unique names, that's even

> Right now, it compiles everything as C++ files, but I could add some
> logic to make it more intelligent in that regard. For instance
> .h -> compile as C
> .hpp -> compile as C++

No, I wasn't suggesting that. I think the default should be C++ regarding
the header extension, but with an option to use C if desired. My code is all
C++, and even if I did write C code it would definitely be compatible with
C++. But, others may want to compile header files as C, for whatever reason
they may have.


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at