Note that there are some explanatory texts on larger screens.

plurals
  1. POMicrosoft Visual Studios 2012 Can't open "python33.lib"
    primarykey
    data
    text
    <p>I'm using the Boost libraries in MicroSoft Visual Studios 2012 for a C++ program that is going to have Python embedded into it. The problem is when I try to Build Solution [F7]; I get this ::</p> <p><code>Error 1 error LNK1104: cannot open file 'python33.lib' C:\Users\usr\Documents\Visual Studio 2012\Projects\ConsoleApplication1\ConsoleApplication1\LINK</code></p> <p>The problem is, I have no idea what this is, means, or any clue of how to fix it. I have already tried to move my python folder into my Desktop, as it was originally in the C:\, I thought maybe it was a permissions error, but that didn't do anything.</p> <p>Here is my code from a tutorial that I was reading in preparation for the porject::</p> <pre><code>// ConsoleApplication1.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include &lt;boost/lambda/lambda.hpp&gt; #include &lt;boost/python.hpp&gt; using namespace boost::python; int main( int argc, char ** argv ) { try { Py_Initialize(); object main_module(( handle&lt;&gt;(borrowed(PyImport_AddModule("__main__"))))); object main_namespace = main_module.attr("__dict__"); handle&lt;&gt; ignored(( PyRun_String( "print \"Hello, World\"", Py_file_input, main_namespace.ptr(), main_namespace.ptr() ) )); } catch( error_already_set ) { PyErr_Print(); } } </code></pre> <p>--Visual Studios 2012 --Windows 7 x64 --Python 3.3.2 --Boost libraries --Python Embedded C++ program</p> <p>--Link to tutorial page:: <a href="http://wiki.python.org/moin/boost.python/EmbeddingPython" rel="nofollow">http://wiki.python.org/moin/boost.python/EmbeddingPython</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload