Paul, Both or neither - for me it's important that RDKit::foo() is working in my code, not which specific library it is in or what other libraries the first lib depends upon. So if I need to use foo() I'd like to know what to include into my Makefile. That's why I suggested having a monolithic static library as an option or an easy way to get a list of libs to add to the linker command.
Igor On Fri, Aug 19, 2016 at 11:22 AM, Paul Emsley <[email protected]> wrote: > > I'd like to pick apart this comment: > > On 19/08/2016 15:45, Igor Filippov wrote: > > > It is sometimes a bit of a pain to collect the list of the dependencies. > > Do you mean that (for example) if you wanted to link with > libMolChemicalFeatures, you also > have to add libSubstructureMatch and libSmilesParse - and it isn't readily > apparent to you > which additional libraries you need to add when linking? > > > Alternatively some easier way to discover what belongs to what library > would be appreciated... > > Do you mean which libraries depend on which libraries (as above) - or > which functions are in > which libraries? > > > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Rdkit-discuss mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/rdkit-discuss >
------------------------------------------------------------------------------
_______________________________________________ Rdkit-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
