Martin Nolte authored 7 years ago and Andreas Dedner committed 7 years ago

The builder exceptions should be shared between different implementations of the
builder interface. This patch migrates them to a separate module
`dune.generator.exceptions`. For convenience they are also imported into
`dune.generator` itself.

Rationale: If the user chooses to pass in some other `source` object to
           generate the code on-demand, he can only save the code
           generation if he already ensured the generated source code
           would be identical to an existing copy.

In the original form a failure in the code generation (triggered during
writting by calling code.__str__() could lead to a generated cc file with
no CMakeLists.txt entry - rerunning the code then led to a
"no rule to make target" error and required removing the cc file by hand.

doesn't work with the decorator idea)

dune.generator.__init__

simpleGenerator

also only add plot/triangulation method to 2d grids

std::pair<class__,bool> cls = insertClass<DuneType>(scope, pythonName, pybind_options...,
   GenerateTypeName(...), InsertFiles{...} )

Provide a single method that generates the entry and adds the property to
the exported class

scripts in batch mode
Also always add the python module to the generated class

This avoids duplicating the 'false' case.

Instead of generating one CMake target "generated_module", we now define a
CMake target for every module create in dune-py. Before loading the module,
we always call cmake to make sure the module is rebuilt if dependencies change.

Note: Changes in the source code of the generated module remain untracked for
      now.