$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [gil] Ok to merge new gil's extension to release branch?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-04-02 10:21:03
AMDG
On 04/02/2013 06:17 AM, Christian Henning wrote:
>
> I've committed this to the trunk and updated
>> Boost.IOStreams to use it.
>>
>>
> Thanks! I have taken a quick look and will add the changed to my jam file
> tonight. I think I still have to apply your changes to the other 3rd party
> jam file ( png, jpeg, and tiff ).
>
> Quick question:
>
> I usually compile 32bit and 64bit for both DEBUG and RELEASE
> configurations. How would I configure the binary name depending on the
> architecture and configuration? I imagine a naming convention like we do
> for the general boost libs.
>
Just copy what I did for Boost.IOStreams:
<build-name>boost_zlib <tag>@tag
(the tag rule is inherited from Jamroot)
Everything inside Boost needs to be consistent
about this.
In Christ,
Steven Watanabe