On 10/11/2011 18:20, My Th wrote: > Hi! > > These plugins are not wrapped for static compilation: > ABINITFormat > CacaoInternalFormat > CanSmilesNS > CASTEPFormat > EEMCharges > FPCount > GROFormat > InChICompareFormat > InChIKeyFormat > L5 > MyFpType > NoCharges > OpAddFileName > OpGenAlias > OpLargest > OpNewV > OpSmallest > SecondOpAlign > Tautomers > XSFFormat > XXXFormat > > Is there a reason to not wrap any of them? (Apart of XXXFormat which is > an example plugin.) Some of them clearly look just forgotten there.
Some of these are only in example code, MyFPType, FPCount, or are not in my version of the code, OpNewV, SecondOpAlign. Tautomers is not (yet) a plugin. I guess the code in plugin.h and plugin.cpp for the static build is hand generated, but for maintainability it really ought to be automated. There may be better ways, but a possibility would be to add a macro to the declaration of each plugin global instance, e.g. STATICLIBASSIST SMIFormat theSMIFormat; STATICLIBASSIST would be defined as nothing, but a pre-build step in a static library build could grep the cpp files to provide the information to construct the code needed. Any new plugins would be written with the macro and so would be automatically included. Chris ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
