# Boost-Build :

Subject: Re: [Boost-build] Building Zlib and Iostreams
From: Craig Henderson (cdm.henderson_at_[hidden])
Date: 2009-07-13 07:40:10

> > > > > You need to specify ZLIB_INCLUDE as well and maybe ZLIB_LIBPATH.
You
> > don't
> > > > > have
> > > > > to poke at NO_ZLIB, in 1.39. The way you set ZLIB_BINARY above
seems
> > > > > ok. You can use --debug-configuration to see some debugging
messages.
> > > >
> > > > Still no luck. I've set the environment variables
> > > > ZLIB_BINARY=zdll
> > > > ZLIB_INCLUDE=C:\root\Development\Library\zlib\include
> > > > ZLIB_LIBPATH=C:\root\Development\Library\zlib\lib
> > > >
> > > > And rebuilt the whole Boost library set using
> > > > ..\bjam --toolset=msvc stdlib=stlport "stdlib:stlport-iostream=on"
> > > > and I just can't get Boost.Build to produce
> > > > libboost_zlib-vc80-mt-gdp-1_39.lib
> > > >
> > > > I don't know at what point to expect this library to be built - I'm
> > guess it
> > > > is an output from the iostreams build, is that right?
> > > >
> > > > I'm at a loss now - any clues as to how I might debug this to
identify
> > where
> > > > my configuration is wrong?
> >
> > > Did you use --debug-configuration, as I have suggested above?
> >
> > Yes, sorry, and I see
> > notice: [cmdline-cfg] Detected command-line request for msvc: toolset=
msvc
> > version=
> > notice: [cmdline-cfg] toolset msvc already configured
> > notice: [cmdline-cfg] adding toolset=msvc to the build request.
> > notice: iostreams: using prebuilt zlib
>
> Ok, this means zlib is detected, which is good. The library you mention
> previously, libboost_zlib-vc80-mt-gdp-1_39.lib, is not actually supposed
> to be produced, but Boost.Iostreams autolinking code wants it.

> Can you try adding BOOST_ZLIB_BINARY=xxx macro when building your project,
> where xxx is the basename of the zlib library?

That's got it linking. Thanks for your help.
-- Craig