[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost-build
Subject:    [Boost-build] Copy and rename file in install rule
From:       Anthony Foglia <AFoglia () princeton ! com>
Date:       2011-02-25 16:15:59
Message-ID: 4D67D5BF.4080502 () princeton ! com
[Download RAW message or body]

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)
   example_program.cpp
   run.py

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 
on install.

Any suggestions how to go about this?

-- 
Anthony Foglia
Princeton Consultants
(609) 987-8787 x233

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
[prev in list] [next in list] [prev in thread] [next in thread]