RE: [jamboost] gcc compiler settings and bjam V2

From: Mark Elston (m.elston_at_[hidden])
Date: 2004-06-15 14:28:42

Great!! Thanks again.

I've never tried mixing -Wall and -w before. I'll try it out.

What is the difference between the current approach and having a 
'general' <warning-level> option, or something similar? This could 
default to a specific value (-Wall for gcc) or be set as other options
in a project's requirements. Perhaps there is no difference. I just
have an aversion to making hard-coded assumptions about the way
*everyone* will use something :)

Mark

> -----Original Message-----
> From: Vladimir Prus [mailto:ghost_at_[hidden]]On Behalf Of Vladimir
> Prus
> Sent: Tuesday, June 15, 2004 12:10 AM
> To: jamboost_at_[hidden]
> Subject: Re: [jamboost] gcc compiler settings and bjam V2
> 
> 
> Mark Elston wrote:
> > I have been trying to find a way to change the compiler settings
> > for compiling an app with gcc using bjam V2.
> 
> Hi Mark,
> 
> > Everytime I run bjam it uses gcc (or g++) with the -Wall and
> > -ftemplate-depth-100 and -fno-inline. How do I go about
> > changing these parameters?
> 
> The "-fno-inline" is there only for <inlining>off. To turn it on, you can
> 
> 1. Pass "inlining=on" on the command line
> 2. Add "<inlining>on" to project requirements
> 3. Add "<inlining>on" to project "default build"
> 
> The '-Wall' and '-ftemplate-depth-100' are hardcoded in gcc.jam. 
> However, you 
> can pass
> 
> cxxflags=-w cxxflags=-ftemplate-depth-1000
> 
> on the command line and those options will appear on the command 
> line after 
> hardcoded ones, disabling all warnings and increasing template depth, 
> respectively. Of course, those properties can be set in project 
> requirements 
> too.
> 
> HTH,
> Volodya
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
>