Subject: Re: [Boost-build] rule execution order
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-17 23:01:51
On 17.10.2016 22:53, Rene Rivera wrote:
> Almost missed this email. Sorry about the delayed response..
No worries. Thanks for the explanation ! I'll make sure to add the
'numpy' rule to the boostdoc and boostrelease targets.
But first I need to fix the numpy rule to correctly perform the build,
1) a copy of a set of files from the source tree to the build tree
2) the invocation of a command ('make' or 'sphinx-build') inside that
3) a copy of a set of generated files from the build tree to the
destination (which is AFAIU in the source tree).
and I still don't know how to do the copying imperatively, i.e. not as
part of the ("functional") evaluation of a dependency graph.
The "common" module has some support code to copy files around (though
the "copy" rule itself is empty !?). Is there no way to invoke some
"common.copy" with explicit file arguments (the result of a glob() call) ?
(Among the many reasons I think using the "install" rule for this is
inappropriate is the fact that I don't know upfront what files to copy
back. Which files are generated in the process depends on the content
itself, which I'd rather not inspect to code the build logic.)
-- ...ich hab' noch einen Koffer in Berlin...
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