Re: [Boost-build] alias rule not propagating requirements?

Subject: Re: [Boost-build] alias rule not propagating requirements?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2008-12-02 20:10:55

AMDG

John Maddock wrote:
> I'm trying to create an alias rule that will override/set certain pdf 
> generation properties, for example:
>
> alias type_traits : $(boost-root)/libs/type_traits/doc//standalone : 
> $(COMMON_PDF_SETTINGS) ;
>
> But $(COMMON_PDF_SETTINGS) don't get passed down to the pdf build.  
> Same result if I spell out the settings explicitly:
>
> alias type_traits : $(boost-root)/libs/type_traits/doc//standalone : 
> <xsl:param>body.start.indent=0pt ;
>
> Any ideas on this?

Grr.  alias behaves like other main target rules and only propagates 
features that
have the propagated attribute.  This makes non-propagated features 
useless in
the requirements and default-build of an alias target.

You can add the properties like this, I think:

alias type_traits : 
$(boost-root)/libs/type_traits/doc//standalone/$(COMMON_PDF_SETTINGS:J=/) ;

> Also, I would like if possible to be able to control the file name 
> under which a pdf gets installed: I can use the "install" rule to copy 
> the pdf to a location of my choice, but the resulting file name isn't 
> always quite what I would like... is there any kind of rename-rule I 
> can use?

You can use the <name> property.

install pdf : pdf_doc : <name>renamed_pdf.pdf ;

In Christ,
Steven Watanabe