2008/7/21 Greg Landrum <[email protected]>: > The problem with bjam not being able to find boost-build.jam is > because your BOOST_BUILD_PATH is set incorrectly; it should be set to > "%BOOSTHOME%"; then you won't need BOOST_ROOT.
So, you're saying that I don't need anyt of the BOOST variables to point to the compiled boost stuff. They should just point to the source. >> You also need to set PYTHONHOME to run the tests. Which I'm afraid >> still don't work for me. > > Yes; the test suite assumes on windows that Python is in c:\python25 > or that you have PYTHONHOME set properly; I need to add this to the > wiki. > >> Seems to be due to spaces in the name again. >> It's a pretty crazy test suite so I wasn't able to dig too >> deep...here's an example error message: >> """ >> C:\Documents and Settings\Noel\Desktop\Tools\RDKit\trunk\Code>set >> PYTHONHOME=C:\Program Files\Python25 >> >> C:\Documents and Settings\Noel\Desktop\Tools\RDKit\trunk\Code>python >> ..\Python\TestRunner.py test_list.py >> C:\Program: can't open file 'Files\Python25\python.exe': [Errno 2] No such >> file >> or directory >> C:\Program: can't open file 'Files\Python25\python.exe': [Errno 2] No such >> file >> or directory >> """ >> If I put quotation marks around the PYTHONHOME directory, it fouls up >> Python itself, and won't start up properly (the error message is >> "cannot import os") > > hmm, that's irritating. It also looks to be at least partially a > python problem, not an RDKit problem. Maybe this is why the default > installation path for python is c:\python25? Just because they knew it'd be a problem for RDKit? :-) It's never been an issue before... BTW, it seems to import fine, so I think the compilation, etc. might have worked. > -greg >
