|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-06-24 05:25:52
Folks,
this morning I was thinking that some day (I hope soon), we'll have all the
features ready and need to optimize Boost.Build V2. For example, I planned to
implement certain parts of toolset.jam in C, and maybe
property.jam/feature.jam too.
But why restrict ourself to C? Boost.Build actually works on Windows and
verious Unix flavours, all of which have some C++ compiler. Maybe one that
can't grok explicit member specialization or "mutable", but which can handle
classes and virtual methods just fine. I think that can bring us a lot of
benefits when it comes to hacking in bjam core.
And to add to my opinion, just now I've seen this:
http://gcc.gnu.org/ml/gcc/2004-06/msg01466.html
Even gcc developers consider requiring C++. If they consider it, than surely
every other project can just switch. Also, one of the primary goals of
Boost.Build is to be build system for C++ Boost -- which is collection of C++
libraries. Surely user needs a C++ compiler anyway.
Thoughts?
- Volodya
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk