10 Feb
2014
10 Feb
'14
8:38 a.m.
On 2014-02-10 08:20, Alligand Edouard wrote:
1. Write a parser for the most important rules (exe, lib and so on) based on Boost.Spirit 2. Use the parser's actions to create a dependency tree based on Boost.Graph 3. Attach Python functions to the nodes in the dependency tree based on Boost.Python 4. Implement Python functions for one toolset (like g++) What about using that parser to create a tool that would transform bjam files into different files (ninja, make, cmake, etc.)?
That would be very useful in order to integrate Boost libraries into existing projects.
--Edouard
Nice idea, +1 And for people like me who cannot wrap their head around the logic of bjam files: Translate from ninja, cmake and co to bjam...