编译与zlib的提升 [英] compiling boost with zlib

问题描述

即时通讯的Windows 7（64位，应该是无关）正在编制与bjam的提升

im compiling boost with bjam under windows 7 (64bit-should be irrelevant)

D：\\研发\\提升\\ boost_1_44 \\库\\输入输出流\\建立>的bjam阶段--toolset = MSVC-10.0链接=静态--build型=完整的-s ZLIB_SOURCE = C：\\ zlib125的DLL -s ZLIB_LIBPATH = C：\\ zlib125-DLL \\ LIB -s ZLIB_INCLUDE = C：\\ zlib125-DLL \\包括-s ZLIB_BINARY = C：\\ zlib125的DLL

D:\development\boost\boost_1_44\libs\iostreams\build>bjam stage --toolset=msvc-10.0 link=static --build-type=complete -s ZLIB_SOURCE=C:\zlib125-dll -s ZLIB_LIBPATH=C:\zlib125-dll\lib -s ZLIB_INCLUDE=C:\zlib125-dll\include -s ZLIB_BINARY=C:\zlib125-dll

但我只得到

舞台/ libboost_iostreams-VC100-MT-GD-1_44.lib
bin.v2 /库/输入输出流/编译/ MSVC-10.0 /调试/线程的多/ boost_iostreams-VC100-MT-GD-1_44.dll
bin.v2 /库/输入输出流/编译/ MSVC-10.0 /调试/线程的多/ boost_iostreams-VC100-MT-GD-1_44.lib

stage/libboost_iostreams-vc100-mt-gd-1_44.lib bin.v2/libs/iostreams/build/msvc-10.0/debug/threading-multi/boost_iostreams-vc100-mt-gd-1_44.dll bin.v2/libs/iostreams/build/msvc-10.0/debug/threading-multi/boost_iostreams-vc100-mt-gd-1_44.lib

bin.v2 /库/输入输出流/建设/ zlib的/ MSVC-10.0 /调试/线程的多/ boost_zlib-VC100-MT-GD-1_44.dll
bin.v2 /库/输入输出流/编译/ zlib的/ MSVC-10.0 /调试/线程的多/ boost_zlib-VC100-MT-GD-1_44.lib

bin.v2/libs/iostreams/build/zlib/msvc-10.0/debug/threading-multi/boost_zlib-vc100-mt-gd-1_44.dll bin.v2/libs/iostreams/build/zlib/msvc-10.0/debug/threading-multi/boost_zlib-vc100-mt-gd-1_44.lib

但
舞台/ libboost_zlib-VC100-MT-GD-1_44.lib
丢失了。

我在编译出错了？

当我尝试运行我的项目，与升压和自编升压/线程图书馆的运作良好，我得到以下错误，当我包括升压zlib的东西。

when i try running my project that worked well with boost and self-compiled boost/thread librarys i get following error when i include the boost zlib stuff

6> LINK：致命错误LNK1104：无法打开文件'libboost_zlib-VC100-MT-GD-1_44.lib

6>LINK : fatal error LNK1104: cannot open file 'libboost_zlib-vc100-mt-gd-1_44.lib'

没有人知道我在做什么错了？

does anyone know what i'm doing wrong?

推荐答案

我花了一段时间才能加速与支持zlib建立正确。我的博客上讲述它的这里。

It took me a while to get Boost to build correctly with zlib support. I blogged about it here.

要概括起来讲，我跑进问题是，在一些点的zlib不再包含一个 gzio.c 源文件。为加速构建系统（jamfile.v2）的Jamfile中不得不引起它失败gzio模块的引用。该解决方案是构建之前，删除该引用。

To sum it up, the problem I ran into was that at some point zlib no longer included a gzio.c source file. The jamfile for the Boost build system (jamfile.v2) had a reference to the gzio module which caused it fail. The solution was to remove that reference before building.

我不知道这个答案是相关的任何更长的时间，除非你试图建立一个旧版本的Boost。我相信原来的版本问题已得到修复在较新版本的Boost。

I'm not sure this answer is relevant any longer, unless you're trying to build an old version of Boost. I believe the original build issue has been fixed in more recent versions of Boost.

这篇关于编译与zlib的提升的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！