Hi, I have been working on getting Avogadro to build on Windows for the next release, and have hit an issue with InChI. It looks like it no longer exports symbols on MSVC Windows builds, but that is relatively easy to fix. I also noticed that there are two inchi_api.h files, one in include and one in include/inchi. If I delete the one in include, then the inchidescriptor.cpp fails to build.
This looks like it needs InChI to be enabled, but is unconditionally built (it includes the inchiformat header). Should the logic for the InChI include directories be moved up from src/formats to src so that the include directories will be set up correctly? Should we only enable the inchi descriptor if InChI is enabled and remove the extra inchi_api.h file in include? I am happy to prepare a patch to fix this, and can base it on trunk. Thanks, Marcus ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
