Subject: [Boost-build] Copy and rename file in install rule
From: Anthony Foglia (AFoglia_at_[hidden])
Date: 2011-02-25 11:15:59
Is there a way to have an install rule copy and rename a source file?
We've been using the <source> dependency in install rules to copy
configurations, and I'd like to add our wrapper scripts to the list of
copied files as well. Currently our layout
project-dir (under a Jamroot in the top level)
Our bjam rules install the compiled example_program in a directory
depending on the variant. (Debug for debug, Release for release, etc.)
Currently the run scripts just check every possible variant directory
(in a given order), or only some, and use the executable in that. If I
move the run script into the install directory, I can avoid that logic.
The drawback is that it won't work in the original location. To avoid
breaking code dependent on this, and to make the change obvious, I would
like to name the checked in version run.py.in, and rename it to run.py
Any suggestions how to go about this?
-- Anthony Foglia Princeton Consultants (609) 987-8787 x233
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