Re: [Boost-users] Problem with boost 1.53 compilation in Windows

Subject: Re: [Boost-users] Problem with boost 1.53 compilation in Windows
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2013-02-08 06:47:01

> -----Original Message-----
> From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On Behalf Of DUNDEK Ivan
> Sent: Friday, February 08, 2013 11:18 AM
> To: boost-users_at_[hidden]
> Subject: [Boost-users] Problem with boost 1.53 compilation in Windows
> 
> Hi.
> We are using boost in our project, and now with 1.53 and some added options we are unable to
compile
> the boost in Windows.
> In Linux, the build is OK.
> It seems, that when compiling under Windows, the path for compiled boost obj files depends on the
> options specified, so if there are many options specified, the path become too long. With reduced
number
> of options, the build is OK.
> Build environment: Windows7 64bit, Boost 1.53, VisualStudio 2010 Express Here is the build
command:
> 
> bjam -d2 --toolset=msvc-10.0 variant=debug,release threading=multi link=static runtime-link=shared
install
> boost.locale.std=on boost.locale.icu=off boost.locale.winapi=off boost.locale.posix=off -a
--with-log --
> with-thread --with-system --with-date_time --with-filesystem --with-program_options
--with-iostreams --
> with-regex --with-serialization --with-locale --with-atomic
> define=BOOST_LOG_NO_SETTINGS_PARSERS_SUPPORT
> --prefix="c:\projects\cpce-cpp-stack\1.3.0\win"
> -sZLIB_SOURCE="c:\projects\cpce-cpp-stack\1.3.0\win\third-party\zlib-1.2.7"
>
<snip>

I think that you need to add the --hash bjam option to avoid too long filenames.

Paul

---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
[phone]  07714330204
pbristow_at_[hidden]