Hi, On Sat, Oct 30, 2010 at 02:31:53PM +0000, tim...@users.sourceforge.net wrote: > Revision: 4287 > http://openbabel.svn.sourceforge.net/openbabel/?rev=4287&view=rev > Author: timvdm > Date: 2010-10-30 14:31:52 +0000 (Sat, 30 Oct 2010) > > Log Message: > ----------- > XML and InChI are now turned off for static builds. These will be > enabled again once the win32 linking issues are resolved. Options are: > WITH_STATIC_LIBXML and WITH_STATIC_INCHI Would this be possible to have for dynamic builds as well, at least for inchi? I patched the inchi CMakeLists.txt to force STATIC for the Debian/Ubuntu builds.
Actually, I think using a static inchi should be default for Unix builds. I think it should not be our business to ship a libinchi.so in the system-wide library path (/usr/lib or /usr/local/lib); the users should either have a system inchi from upstream already, or their build should be static. How much disk space is wasted by linking in a static inchi for the format and desriptor (what else?) Similarly, installing inchi_api.h to /usr/include/inchi seems like a namespace violation to me, is that header file really needed from the OpenBabel point of view? Maybe it should get installed under <openbabel/> in that case to prevent collisions with an official inchi package? Cheers, Michael ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
