On Tue, 9 Dec 2003 20:58:30 +0100, Uwe Sander wrote:
I guess there went something wrong during the build, because you should see some .lib files which are the ones to link against.
Any idea where to start debugging? If I now give this command, D:\C++\Boost\Current>..\bjam.exe "-sTOOLS=gcc" I get this output: --------------------------------------------------------------------- skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/cygwin//usr/local/pydebug/include/python2.2 /cygwin//usr/local/pydebug/include/python2.2 /cygwin//usr/include/python2 .2 /cygwin//usr/include/python2.2 /usr/local/pydebug/include/python2.2 /usr/local/pydebug/include/python2.2 /usr/include/python2.2 /usr/include/p ython2.2 /usr/include" You can configure the location of your python installation by setting: PYTHON_ROOT - currently "/usr" PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.2" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "/usr/libs" For detailed configuration of Boost.Python for Cygwin GCC under Windows NT please see http://www.boost.org/libs/python/doc/building.html --------------------------------------------------------------------- ...found 2012 targets... Notice that it doesn't seem to actually build anything. I assume that this is because it's detecting that everything is already built, but I don't know. Thanks, Scott