Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-07-18 02:28:35


On Friday 18 July 2008 10:17:35 Jurko Gospodnetić wrote:
> Hi Joel.
>
> > Hi, bjam -d+2 reveals that with gcc, I get:
> >
> > -ftemplate-depth=128
> >
> > There are some cases where this is not enough. How can I change it?
> > I am doing:
> >
> > : requirements <toolset>gcc:<cxxflags>-ftemplate-depth-300
> >
> > and when I bjam -d+2, I get both:
> >
> > -ftemplate-depth=128 and later, -ftemplate-depth=300
> >
> > while this works, it does not seem to be right.
>
> As this gcc parameter seems to be hardcoded in the gcc toolset's
> (gcc.jam) compile.c++ action code I do not believe there is a way for
> you to change it without changing the toolset itself.
>
> I guess this should be made into a built feature. Then you cuold do
> the following ': requirements <toolset>gcc:<template-depth>300'. I can
> do this but I need to know some information first.
>
> 1. Should this feature be implicit? Other ways to read this question:
> * Can it cause link-time incompatibilities?
> * Does it make a difference which of the two correctly built object
> files you include in your project in case they have been built with
> different template-depth property values.
> * Should Boost Build create a separate build folder for each template
> depth value.
>
> 2. What are the valid values for this feature?
>
> 3. Anyone else have any ideas on how to solve this problem better/'in
> a more generic manner'?

Honestly, I don't think this is a problem worth solving. The second -ftemplate-depth
takes priority, and it's the first time somebody wanted different template depth,
so why care?

- Volodya


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk