Subject: [Boost-build] RFC: Cleaning up the project.target rule.
From: Jurko Gospodnetiæ (jurko.gospodnetic_at_[hidden])
Date: 2012-08-06 12:04:12
Anyone have anything against simplifying the project.target() rule to
return an error in case no project instance has already been created for
the given module instead of lazily creating a parentless project for it?
I just tested it and no internal Boost Build tests use this case nor
does the latest Boost library build require it.
As I see it, projects are always created using project.find() or a
direct project.initialize() call, and the project.target rule is called
only for modules that already have an assigned project instance.
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