[odb-users] internal compiler error: cult:compiler::context::no_entry

MM finjulhich at gmail.com
Wed Aug 29 15:56:40 EDT 2018

On Mon, 6 Aug 2018 at 13:13, Boris Kolpackov <boris at codesynthesis.com>

> MM <finjulhich at gmail.com> writes:
> > odb -d sqlite --sqlite-override-null --std c++14 --profile boost
> > --omit-drop --generate-query --generate-schema-only --schema-format sql
> > --at-once -I/src -I/usr/include --changelog-dir /src/odb --options-file
> > /src/vendors/odb/boost-multiarray.options --input-name mydbname
> > /src/file_1.hpp ... /src/file_n.hpp
> >
> > Does the odb compiler use each header file argument separately? or does
> it
> > concatenate all the headers to produce the SQL.
> Since you have specified the --at-once option, they are effectively
> concatenated in the order specified on the command line.

Still to try to reduce to a reportable example, 1 more question:

In this resulting concatenated stream of c++ code, what happens to #include
directives? They are processed as usual?


More information about the odb-users mailing list