Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Our new scheme is to have any "out" content in a subdirectory called build/
(build/build/ for the build system core, build/<module>/build/ for modules).
This way we can ignore them in .gitignore with a generic entry.
|
|
|
|
|
|
While we could automatically set it if the target is imported, there is
nothing we can do if the target is used in the same project. So to avoid
confusion we make it mandatory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Specifically, now we can write:
{{ c++ 1 --
#include <map>
--
recipe
apply (action, target&) const override
{
...
}
}}
|
|
We are reusing the buildspec syntax for that.
|
|
|
|
|
|
|
|
Also deduce the recipe name.
|
|
|
|
|
|
|
|
This will allow us to deal with backward-incompatible changes to cxx_rule
interface and semantics.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|