错误编译Boost.Python的快速入门 [英] Error compiling Boost.Python quickstart

查看:319
本文介绍了错误编译Boost.Python的快速入门的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我一直在试图编译Boost.Python的快速入门($ BOOST_PATH \\库\\ python的\\例子\\快速启动)实例和所遇到的问题。

首先,我的环境:


  • 操作系统:Windows 7旗舰版64位

  • Python版本:2.7 32位

  • C ++编译器:VC10

  • 加速版本:1.53.0

起初,我不得不编译Boost.Python的库文件问题,但偶然发现的这个的堆栈溢出线程它通过解释如何在VS2010设置包括目录和指向升压编译我的Python目录解决了我的问题。然后我去编译使用该命令的Boost.Python的快速入门例子:

 的bjam工具集= MSVC --verbose检验测试

第几次我试图这样我打了一个解析的外部符号错误,告诉我​​它无法找到,即使它本来应该是在我按我的第一个环节设置库目录升压蟒蛇libary。现在,它给了我以下的输出:

 错误:没有最好的替代/ python_for_extensions
    下一个选择:所需的属性:其中,蟒蛇> 2.7 lt;目标-OS>的窗户
        匹配
    下一个选择:所需的属性:其中,蟒蛇> 2.7 lt;目标-OS>的窗户
        匹配
错误:/ python_for_extensions没有最好的选择
    下一个选择:所需的属性:其中,蟒蛇> 2.7 lt;目标-OS>的窗户
        匹配
    下一个选择:所需的属性:其中,蟒蛇> 2.7 lt;目标-OS>的窗户
        匹配
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\property.jam:649:从模块对象(属性映射)的查找替换@ 1
错误:不明确的密钥lt;目标型> PYTHON_EXTENSION< ABI> MS<非同步的异常和GT;关闭<二进制格式> PE<调试店>对象<调试符号>针对<嵌入舱单>针对<异常处理>在<的extern-C-抛出异常>关闭<硬code-DLL路径>真<主机OS>窗口<包括> ../../../ ..<内联>关闭<安装依赖性>关闭<库>对象(文件目标)@ 1112 LT;库>对象(文件目标)@ 1114<库>对象(文件目标)@ 1116 <链接>共享<主靶型> PYTHON_EXTENSION< MIDL健壮>是< MIDL-无存根代理>是<优化>关闭< OS> NT< PCH>针对< preserve试验目标和GT;针对<分析>关闭<蟒蛇调试>关闭< python.inter preTER> C:\\ Python27 \\ python的<蟒蛇> 2.7< RTTI>针对<运行调试&GT ;针对<运行时链接>共享< STDLIB>天然<带>关闭< SUP preSS-进口的lib>真<符号链接,地点>的项目相对<目标-OS>窗口<目标>对象(文件目标)@ 1132 LT; threadapi>的Win32<螺纹>多<工具,MSVC:版本> 10.0<工具> MSVC<使用者界面>控制台<变>调试和LT;警告 - AS-错误>关闭<警告和GT;针对< xdll路径> / C:/ Program Files文件(x86)的/boost/boost_1_53_0/bin.v2/libs/python/build/msvc-10.0/debug/threading-multi
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\property.jam:626:从模块对象(属性图)@ 1 object(property-map)@1.find
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\type.jam:335:从模块类型中产生的目标-PS-实
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\type.jam:360:从模块类型生成的目标-PS
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\type.jam:270:从模块类型type.generated目标后缀
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\virtual-target.jam:511:在虚拟target.add- $ P $从模块虚拟目标PFIX和后缀
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\virtual-target.jam:470:从模块对象(文件目标)@ 1132 _adjust名
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\virtual-target.jam:253:抽象文件目标从模块对象(文件目标)@ 1132 .__ init__
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\virtual-target.jam:564:从模块对象(文件目标)@ 1132 object(file-target)@1132.__init__
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/kernel\\class.jam:88:在class.new从模块类
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:565:从模块对象generator.generated-目标(MSVC联发生器)@ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/tool​​s\\builtin.jam:869:从模块的对象链接-generator.generated的目标(MSVC联发生器)@ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/tool​​s\\msvc.jam:1061:从模块对象产生的目标(MSVC联发生器)@ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:463:从模块对象结构型结果(MSVC联发生器)@ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:416:在运行真正从模块对象(MSVC联发生器)@ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:390:在generator.run从模块对象(MSVC联发生器)@ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/tool​​s\\builtin.jam:784:从模块对象object(msvc-linking-generator)@1127.run(MSVC联发生器) @ 1127
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:978:在试戴一发电机真正从模块发电机
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:1040:在尝试一发电机从模块发电机
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:1254:在结构,真正从模块发电机
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\generators.jam:1338:在generators.construct从模块发电机
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:1495:从模块对象(输入目标)@ 71结构
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:1298:从模块对象(输入目标)@ 71 object(typed-target)@71.generate
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:732:在产生,真正从模块对象(主要目标)@ 932
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:704:从模块对象(主要目标)@ 932 object(main-target)@932.generate
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:848:在targets.generate - 从引用从模块的目标
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:1217:从模块对象产生依赖性(输入目标)@ 77
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:1269:从模块对象(输入目标)@ 77 object(typed-target)@77.generate
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:732:在产生,真正从模块对象(主要目标)@ 934
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:704:从模块对象(主要目标)@ 934 object(main-target)@934.generate
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:848:在targets.generate - 从引用从模块的目标
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:1217:在产生依赖性的模块对象(化名目标类)@ 81
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:1269:在object(alias-target-class)@81.generate从模块对象(化名目标类) @ 81
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:732:在产生,真正从模块对象(主要目标)@ 936
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2/build\\targets.jam:704:从模块对象(主要目标)@ 936 object(main-target)@936.generate
C:/ Program Files文件(x86)的/boost/boost_1_53_0/tool​​s/build/v2\\build-system.jam:736:负载从模块构建系统
C:\\ Program Files文件(x86)\\boost\\boost_1_53_0\\libs\\python\\example\\quickstart\\..\\..\\..\\..\\tools\\build\\v2/kernel\\modules.jam:283:从模块导入模块
C:\\ Program Files文件(x86)\\boost\\boost_1_53_0\\libs\\python\\example\\quickstart\\..\\..\\..\\..\\tools\\build\\v2/kernel/bootstrap.jam:142:从助推模块的构建
C:\\ Program Files文件(x86)的\\提升\\ boost_1_53_0 \\库\\ python的\\例子\\快速入门\\升压build.jam中:7:从模块模块范围

编辑1:

原来,当你在* -config.jam文件的多个定义你的Python目录我上面张贴的错误信息时。现在,我得到原始的错误消息:

  ...耐心... ...
...忍耐...
...发现1745的目标...
...更新10个目标...
编译C-C ++ BIN \\ MSVC-10.0 \\调试\\线程的多\\ extending.obj
extending.cpp中
msvc.link.dll斌\\ MSVC-10.0 \\调试\\线程的多\\ extending.pyd
   创建库斌\\ MSVC-10.0 \\调试\\穿线多\\ extending.lib和对象斌\\ MSVC-10.0 \\调试\\线程的多\\ extending.exp
msvc.manifest.dll斌\\ MSVC-10.0 \\调试\\线程的多\\ extending.pyd
捕获输出纸盒\\ test_ext.test \\ MSVC-10.0 \\调试\\线程的多\\ test_ext
        1文件(S)复制。
====== BEGIN输出======
试:
    从进口延伸*
期待什么

试:
    HI =你好('加利福尼亚)
期待什么

试:
    hi.greet()
期待:
    你好从加州

试:
    邀请(HI)
期待:
    你好来自加利福尼亚州!请快来!

试:
    hi.invite()
期待:
    你好来自加利福尼亚州!请快来!

试:
    类罗嗦(你好):
        高清迎接(个体经营):
            返回hello.greet传递(个体经营)+',那里的天气是好的
期待什么

试:
    HI2 =罗嗦('佛罗里达')
期待什么

试:
    hi2.greet()
期待:
    你好,从佛罗里达州,那里的天气是好的

试:
    邀请(HI2)
期待:
    你好从佛罗里达!请快来!

1项没有测试:
    test_extending.run
1项通过了所有测试:
   9测试中test_extending
9测试在2项。
9过去了,0失败。
测试通过。退出状态:0
======结束输出======
** **通过BIN \\ test_ext.test \\ MSVC-10.0 \\调试\\线程的多\\ test_ext.test
msvc.link斌\\ test_embed.test \\ MSVC-10.0 \\调试\\线程的多\\ test_embed.exe
LINK:警告LNK4001:未指定目标文件;使用的库
LINK:错误LNK2001:无法解析的外部符号_mainCRTStartup
BIN \\ test_embed.test \\ MSVC-10.0 \\调试\\穿线多\\ test_embed.exe:致命错误LNK1120:1无法解析的外部        所谓的C:\\ Program Files文件(x86)的\\微软的Visual Studio 10.0 \\ VC \\ vcvarsall.bat86> NUL
链接/ NOLOGO /增量:NO / DEBUG / MACHINE:X86 /子系统:控制台/out:\"bin\\test_embed.test\\msvc-10.0\\debug\\threading-multi\\test_embed.exe/ LIBPATH:C:\\ Python27 \\库@BIN \\ test_embed.test \\ MSVC-10.0 \\调试\\穿线多\\ test_embed.exe.rsp
        如果%ERRORLEVEL%NEQ 0 EXIT%ERRORLEVEL%...失败msvc.link斌\\ test_embed.test \\ MSVC-10.0 \\调试\\穿线多\\ test_embed.exe斌\\ test_embed.test \\ MSVC-10.0 \\调试\\穿线多\\ test_embed.pdb ...
...去除斌\\ test_embed.test \\ MSVC-10.0 \\调试\\线程的多\\ test_embed.pdb
...跳过< PBIN \\ test_embed.test \\ MSVC-10.0 \\调试\\穿线多> test_embed.run的不足和LT; PBIN \\ test_embed.test \\ MSVC-10.0 \\调试\\穿线多> test_embed.exe。 ..
...未能更新2个目标...
...跳过2个目标...
...更新6个目标...


解决方案

我不知道这个问题是一个什么)。问题二)似乎是在升压例子中的错误,卡纸文件正试图从一个可执行文件,而不是静态库或cpp文件进行测试的可执行文件。

证明什么,我不得不这样做来获得运行嵌入的例子。

I've been trying to compile the Boost.Python 'quickstart' ($BOOST_PATH\libs\python\examples\quickstart) examples and have run into an issue.

First, my environment:

  • OS: Windows 7 Ultimate 64 bit
  • Python version: 2.7 32 bit
  • C++ Compiler: VC10
  • Boost version: 1.53.0

Initially, I had issues compiling the Boost.Python library files but happened upon this Stack Overflow thread which solved my issue by explaining how to set include directories in VS2010 and point the boost compile to my python directory. I then went to compile the Boost.Python quickstart examples using the command:

bjam toolset=msvc --verbose-test test

The first couple of times I attempted this I hit an unresolved external symbol error telling me it couldn't find the boost python libary even though it should have been the in the library directory I set per my first link. Now it's giving me the following output:

error: No best alternative for /python_for_extensions
    next alternative: required properties: <python>2.7 <target-os>windows
        matched
    next alternative: required properties: <python>2.7 <target-os>windows
        matched
error: No best alternative for /python_for_extensions
    next alternative: required properties: <python>2.7 <target-os>windows
        matched
    next alternative: required properties: <python>2.7 <target-os>windows
        matched
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\property.jam:649: in find-replace from module object(property-map)@1
error: Ambiguous key <target-type>PYTHON_EXTENSION <abi>ms <asynch-exceptions>off <binary-format>pe <debug-store>object <debug-symbols>on <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <hardcode-dll-paths>true <host-os>windows <include>../../../.. <inlining>off <install-dependencies>off <library>object(file-target)@1112 <library>object(file-target)@1114 <library>object(file-target)@1116 <link>shared <main-target-type>PYTHON_EXTENSION <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python.interpreter>C:\Python27\python <python>2.7 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <suppress-import-lib>true <symlink-location>project-relative <target-os>windows <target>object(file-target)@1132 <threadapi>win32 <threading>multi <toolset-msvc:version>10.0 <toolset>msvc <user-interface>console <variant>debug <warnings-as-errors>off <warnings>on <xdll-path>/C:/Program Files (x86)/boost/boost_1_53_0/bin.v2/libs/python/build/msvc-10.0/debug/threading-multi
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\property.jam:626: in object(property-map)@1.find from module object(property-map)@1
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\type.jam:335: in generated-target-ps-real from module type
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\type.jam:360: in generated-target-ps from module type
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\type.jam:270: in type.generated-target-suffix from module type
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\virtual-target.jam:511: in virtual-target.add-prefix-and-suffix from module virtual-target
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\virtual-target.jam:470: in _adjust-name from module object(file-target)@1132
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\virtual-target.jam:253: in abstract-file-target.__init__ from module object(file-target)@1132
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\virtual-target.jam:564: in object(file-target)@1132.__init__ from module object(file-target)@1132
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/kernel\class.jam:88: in class.new from module class
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:565: in generator.generated-targets from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/tools\builtin.jam:869: in linking-generator.generated-targets from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/tools\msvc.jam:1061: in generated-targets from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:463: in construct-result from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:416: in run-really from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:390: in generator.run from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/tools\builtin.jam:784: in object(msvc-linking-generator)@1127.run from module object(msvc-linking-generator)@1127
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:978: in try-one-generator-really from module generators
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:1040: in try-one-generator from module generators
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:1254: in construct-really from module generators
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\generators.jam:1338: in generators.construct from module generators
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:1495: in construct from module object(typed-target)@71
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:1298: in object(typed-target)@71.generate from module object(typed-target)@71
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:732: in generate-really from module object(main-target)@932
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:704: in object(main-target)@932.generate from module object(main-target)@932
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:848: in targets.generate-from-reference from module targets
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:1217: in generate-dependencies from module object(typed-target)@77
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:1269: in object(typed-target)@77.generate from module object(typed-target)@77
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:732: in generate-really from module object(main-target)@934
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:704: in object(main-target)@934.generate from module object(main-target)@934
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:848: in targets.generate-from-reference from module targets
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:1217: in generate-dependencies from module object(alias-target-class)@81
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:1269: in object(alias-target-class)@81.generate from module object(alias-target-class)@81
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:732: in generate-really from module object(main-target)@936
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2/build\targets.jam:704: in object(main-target)@936.generate from module object(main-target)@936
C:/Program Files (x86)/boost/boost_1_53_0/tools/build/v2\build-system.jam:736: in load from module build-system
C:\Program Files (x86)\boost\boost_1_53_0\libs\python\example\quickstart\..\..\..\..\tools\build\v2/kernel\modules.jam:283: in import from module modules
C:\Program Files (x86)\boost\boost_1_53_0\libs\python\example\quickstart\..\..\..\..\tools\build\v2/kernel/bootstrap.jam:142: in boost-build from module
C:\Program Files (x86)\boost\boost_1_53_0\libs\python\example\quickstart\boost-build.jam:7: in module scope from module

EDIT 1:

Turns out the error message I posted above occurs when you define your python directory in more than one of the *-config.jam files. Now I get the original error message:

...patience...
...patience...
...found 1745 targets...
...updating 10 targets...
compile-c-c++ bin\msvc-10.0\debug\threading-multi\extending.obj
extending.cpp
msvc.link.dll bin\msvc-10.0\debug\threading-multi\extending.pyd
   Creating library bin\msvc-10.0\debug\threading-multi\extending.lib and object bin\msvc-10.0\debug\threading-multi\extending.exp
msvc.manifest.dll bin\msvc-10.0\debug\threading-multi\extending.pyd
capture-output bin\test_ext.test\msvc-10.0\debug\threading-multi\test_ext
        1 file(s) copied.
====== BEGIN OUTPUT ======
Trying:
    from extending import *
Expecting nothing
ok
Trying:
    hi = hello('California')
Expecting nothing
ok
Trying:
    hi.greet()
Expecting:
    'Hello from California'
ok
Trying:
    invite(hi)
Expecting:
    'Hello from California! Please come soon!'
ok
Trying:
    hi.invite()
Expecting:
    'Hello from California! Please come soon!'
ok
Trying:
    class wordy(hello):
        def greet(self):
            return hello.greet(self) + ', where the weather is fine'
Expecting nothing
ok
Trying:
    hi2 = wordy('Florida')
Expecting nothing
ok
Trying:
    hi2.greet()
Expecting:
    'Hello from Florida, where the weather is fine'
ok
Trying:
    invite(hi2)
Expecting:
    'Hello from Florida! Please come soon!'
ok
1 items had no tests:
    test_extending.run
1 items passed all tests:
   9 tests in test_extending
9 tests in 2 items.
9 passed and 0 failed.
Test passed.

EXIT STATUS: 0 
====== END OUTPUT ======
**passed** bin\test_ext.test\msvc-10.0\debug\threading-multi\test_ext.test
msvc.link bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.exe
LINK : warning LNK4001: no object files specified; libraries used
LINK : error LNK2001: unresolved external symbol _mainCRTStartup
bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.exe : fatal error LNK1120: 1 unresolved externals

        call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul
link /NOLOGO /INCREMENTAL:NO /DEBUG /MACHINE:X86 /subsystem:console /out:"bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.exe" /LIBPATH:"C:\Python27\libs"  @"bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.exe.rsp"
        if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL%

...failed msvc.link bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.exe bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.pdb...
...removing bin\test_embed.test\msvc-10.0\debug\threading-multi\test_embed.pdb
...skipped <pbin\test_embed.test\msvc-10.0\debug\threading-multi>test_embed.run for lack of <pbin\test_embed.test\msvc-10.0\debug\threading-multi>test_embed.exe...
...failed updating 2 targets...
...skipped 2 targets...
...updated 6 targets...

解决方案

I'm not sure what the problem is with a). Problem b) appears to be a bug in the boost example, the jam file is trying to make a test executable from an executable instead of a static lib or cpp file.

I documented what I had to do to get the embed example running.

这篇关于错误编译Boost.Python的快速入门的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆