Re: [Boost-build] Modifying output names for exe targets

From: Phillip Seaver (phil_at_[hidden])
Date: 2007-10-30 13:48:49

Dirk Griffioen wrote, on 10/30/2007 1:21 PM:
> Hi Phillip,
>
> I read the post differently
>
> exe myExe : myExe.cpp : <name>fooBar.exe ;
>
> would mean to me 'build an exe with the name myExe, but on install, 
> rename it to fooBar.exe'
>
> but I might have read into it, since that was my problem - hence my 
> answer ...

The "exe" rule just tells Boost.Build how to build an executable.  It 
doesn't have anything to do with the install, other than as a source, AFAIK.

> the
> <tag>@apago_tag
> way would add to a target, I would like strip as in change the target 
> name on installation
>
> Would it be possible to change the name of a target on installation?

The sample I gave does add to the output name, but it could, e.g., 
always change executable names to "a.exe", if you wanted.  The reason I 
wrote the rule that way is because I was installing all executables into 
the same directory, and have debug and release versions with the same 
name conflicted.  "bjam debug release" would fail because it would see 
that both would have the same installed name and refuse to run.

At least in my copy of Boost.Build (which is a few months behind 
current, I think), the "install" rule doesn't allow <tag> at all and 
doesn't allow <name> if it thinks the target would need to be relinked 
(Boost.Build-compiled executables and libraries).  So, I think the 
answer is "No."  Out of curiosity, why do you want the name to be 
different when it gets built versus installed?  They should be going to 
completely different directories, so there wouldn't be a name conflict...

Phillip