[odb-users] How to separate code in several dynamic libraries

francois cellier franchouze_llf at yahoo.fr
Mon May 28 05:45:33 EDT 2018

Hi Boris,

Thank you for your answer. To answer your question I used the following options on odb : -d ; --at-once; --default-pointer and --std

However I may have solved my problem this morning in the folowing way:- creating two libs with C++ classes and odb annotation called libModelA and libModelB (libModelA has dependency on some classes of libModelB). In those libraries no code has been generated by odb.
- creating a library libOdbB which contains the generated code by odb and some other stuff (the odb software is applied on the annotated C++ files of libModelB)
- creating a library libOdbA which contains the generated code by odb for the libModelA and only the required dependancies (i.e. a subset of libModelB).

By doing this I have some code duplication in the generated files by odb (on the subset of classes of libModelB used by libModelA) but as it is automatically generated code, it is fine with me...


    Le jeudi 24 mai 2018 à 18:27:54 UTC+2, Boris Kolpackov <boris at codesynthesis.com> a écrit :  
 francois cellier <f_cellier at yahoo.fr> writes:

> Do you have any idea of how it should be done ?

Show how (i.e., the ODB compiler command line) you generate the *-odb.*
files for each library.


More information about the odb-users mailing list