On Wed, Nov 23, 2011 at 8:26 PM, Alex Henderson <blueobelisk4a...@gmail.com> wrote: > > ...and that didn't appear until I rebuilt the Boost libraries. So am I > right in thinking that RDKit dynamically links to Boost?
Yes. > A tip for others here is to check the Advanced box in the CMake GUI > since this then allows the Bison and Flex executables' locations (not > just the path) to be set. > > Now I can generate the RDKit.sln file in the build folder. However... > the solution doesn't build :-( > > The easiest place to see the error is in the SMILESParser. The first > error is related to m4, which I'd never heard of. > > C:\Program Files\GnuWin32\bin\bison.exe: m4: No such file or directory > > It appears to be installed with either Flex or Bison and adding that > directory to the path moved us on a step. Yes, you should have the place where flex and bison are installed in your PATH. > Now I get the following error: > > 2>------ Rebuild All started: Project: SmilesParse, Configuration: Debug > Win32 ------ > 2>Deleting intermediate and output files for project 'SmilesParse', > configuration 'Debug|Win32' This is a side point, but I will go ahead and mention it now: notice that you are building the debug configuration. This doesn't affect the compilation process, but you certainly want to switch to a release build before you start using the code. > 2>[BISON][SmartsY] Building parser with bison 2.4.1 > 2>smarts.yy: conflicts: 66 shift/reduce > 2>[BISON][SmilesY] Building parser with bison 2.4.1 > 2>[FLEX][SmartsL] Building scanner with flex C:/GnuWin32/bin/flex.exe > version 2.5.4 > 2>"smarts.ll", line 1: unrecognized %option: reentrant > 2>"smarts.ll", line 2: unrecognized %option: bison-bridge > 2>Project : error PRJ0019: A tool returned an error code from > "[FLEX][SmartsL] Building scanner with flex C:/GnuWin32/bin/flex.exe > version 2.5.4" > 2>Build log was saved at > "file://c:\SourceCode\rdkit\rdkit\build\Code\GraphMol\SmilesParse\SmilesParse.dir\Debug\BuildLog.htm" > 2>SmilesParse - 1 error(s), 0 warning(s) oh, that's unlucky. The problem is that the RDKit now uses a couple features in Flex that are not present in the ancient version that is distributed as part of the gnuwin32 distribution. The most straightforward solution to the problem is to install cygwin or msys and be sure you install the flex and bison packages that are available for them. I guess it's been a while since someone tried compiling the RDKit on windows without using cygwin (those changes were made to the RDKit in May of 2010). I will update the windows build instructions on the wiki. -greg ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Rdkit-discuss mailing list Rdkit-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
