Re: [boost] [gil] Ok to merge new gil's extension to release branch?

Subject: Re: [boost] [gil] Ok to merge new gil's extension to release branch?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-04-04 00:10:08

AMDG

On 04/03/2013 07:27 PM, Christian Henning wrote:
> <snip>
> I rerun again and you can see the output here:
> 
> http://pastebin.com/BWgWdtRz
> 
> I'm trying to build boost libs not the gil:io tests. So the only lib
> that would use zlib is boost::iostreams but I haven't configured it to
> use it.
> 

Oh.  I see what the problem is.  Should be fixed now.

>>
>>> <snip>
>>>
>>
>> Use properties: e.g. /zlib//zlib/<variant>release
>>
> 
> What I mean is to set compiler flags like: CFLAGS= -DMAX_WBITS=14
> -DMAX_MEM_LEVEL=7
> 
> Those flags are zlib specific.
> 

It depends on where you want to specify them.

If you want to specify it in your Jamfile, then:

feature.feature zlib-variant : myzlib : optional propagated composite ;
feature.compose <zlib-variant>myzlib :
  <define>MAX_WBITS=14 <define>MAX_MEM_LEVEL=7 ;

Then use <zlib-variant>myzlib as above.

If you want to specify it in user-config.jam, then use:

uzing zlib : 1.2.5 : <source>... : <define>... ;

In Christ,
Steven Watanabe