Re: [Boost-build] Copy TCL script using install rule

Subject: Re: [Boost-build] Copy TCL script using install rule
From: Alexander Sack (pisymbol_at_[hidden])
Date: 2008-11-14 08:06:08

Sill question, but why not just copy it in place since its not a binary?

-aps

On Thu, Nov 13, 2008 at 7:55 AM, Johan Nilsson
<r.johan.nilsson_at_[hidden]> wrote:
> Hi,
>
> I've got a medium-sized project in which I'm using Boost.Build. Applicable
> versions:
>
> - Boost.Build from Boost 1.34.1
> - bjam is 3.1.14 (should also be from Boost 1.34.1 release)
>
> My project consists of a number of c++ programs and libraries, but I'd like
> to integrate the "build" of a TCL script into the build. Simply, what I'd
> like to do is to use the install rule to copy the script into the dedicated
> install directory.
>
> This is an excerpt from my Jamroot:
>
> ---
> install bin
>       : # targets
>       $(bin-targets) # includes TCL script target below
>       : # requirements
>       <install-type>EXE
>       <install-dependencies>off
>       <variant>debug:<location>$(debug-bin-location)
>       <variant>release:<location>$(release-bin-location)
> ;
> ---
>
> This is my first attempt at a Jamfile for the TCL script:
>
> ---
> import common ;
> import path ;
>
> path-constant SRC : ../src ;
> constant APP : guicli ;
>
> local sources = [ path.join $(SRC) guicli.tcl ] ;
>
> make $(APP) : $(sources) : common.copy ;
> ---
>
> The script gets copied to the variant directoy during build, but is not
> included among the installed files. I guess the "<install-type>EXE" in
> Jamroot's install rule invocation might be the culprit, but I don't know how
> to properly work around this.
>
> / Johan
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>