List Info

Thread: copying files to gristed target directory




copying files to gristed target directory
user name
2006-09-27 18:48:01
Hi Folks,

Is there a way to copy arbitrary files into the gristed
output directory
of a 'run' target?  I know the run target can take 'input
files' that
appear on the command line.  However, in our case the extra
files are
not appropriate as command line parameters, so we want to
copy them to
the same directory as the 'run' target binary.

Thanks for any help,
-steve
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
copying files to gristed target directory
user name
2006-09-28 02:14:20
King, Steven R wrote:
> Is there a way to copy arbitrary files into the gristed
output directory
> of a 'run' target?  I know the run target can take
'input files' that
> appear on the command line.  However, in our case the
extra files are
> not appropriate as command line parameters, so we want
to copy them to
> the same directory as the 'run' target binary.

I do something equivalent but for regular targets, and
copying around 
header files. You can use the "make" target to
copy a file. Something like:

import common ;
make myfile.txt : some-path/myfile.txt : common.copy ;
explicit myfile.txt ;

And a lib target might refer to the file as:

lib my : foo.cpp : <dependcy>myfile.txt ;

HTH.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
copying files to gristed target directory
user name
2006-09-28 02:25:36
Rene Rivera wrote:
> King, Steven R wrote:
>> Is there a way to copy arbitrary files into the
gristed output directory
>> of a 'run' target?  I know the run target can take
'input files' that
>> appear on the command line.  However, in our case
the extra files are
>> not appropriate as command line parameters, so we
want to copy them to
>> the same directory as the 'run' target binary.
> 
> I do something equivalent but for regular targets, and
copying around 
> header files. You can use the "make" target
to copy a file. Something like:
> 
> import common ;
> make myfile.txt : some-path/myfile.txt : common.copy ;
> explicit myfile.txt ;
> 
> And a lib target might refer to the file as:
> 
> lib my : foo.cpp : <dependcy>myfile.txt ;

Of course spelling dependency correctly would help 


-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )