Dear Evgueni, First an administrative thing: please don't send email to rdkit-discuss-bounces; that email address doesn't do anything aside from generate a bounce message to me. The correct address to send email to this list is [email protected].
On Wed, Jul 16, 2008 at 11:28 AM, Evgueni Kolossov <[email protected]> wrote: > > Is it possible to have VS2005 sln so I can have one RDKit.DLL linked > statically to my application so debug will be available as it done in > OpenBabel? Assuming that I'm understanding the question correctly, I don't think so. I'll answer in steps: I no longer support the use of .sln files to build the RDKit. Dealing with synchronizing the linux makefiles and two different sets of visual studio projects just got to be too big of a hassle, so I stopped worrying about the visual studio projects back when the RDKit was switched to use boost.build. If you are really interested, old versions of the project files can be found in the subversion repository: http://rdkit.svn.sourceforge.net/viewvc/rdkit/trunk/Code/Build.VC71/?pathrev=500 but please note that I cannot support these and that they are out of date. As for having one big dll: that's also not something that is supported. The functionality of the RDKit is broken across multiple DLLs. This is a design choice and is, I believe, a good thing. So two pieces of bad news, now something that's not completely bad: You can debug RDKit code using Visual Studio on windows. If you build in debug mode and throw an exception, you'll get the option to launch the debugger. I assume that you can also attach to running processes, but I haven't tried this. Best Regards, -greg
