Design of c'tor.
Force the includes to be those supplied by the user.
Ensure that the relevant information from the xml file is extracted.
Data produced by the generatore intented to be written to specified file.
Destination of the configuration file containing how the test double was generated.
Destination of the xml log for how dextool was ran when generatinng the test double.
Query the controller with the filename of the AST node for a decision if it shall be processed.
Query the controller for a decision if it shall be processed.
A list of includes for the test double header.
Controls generation of google mock.
Generate a pre_include header file from internal template?
Generate a #include of the pre include header
Generate a post_include header file from internal template?
Generate a #include of the post include header
Generate location of symbols as comments
Source files used to generate the test double.
Output directory to store files in.
Files to write generated test double data to.
Name affecting interface, namespace and output file.
Namespace for the generated test double.
Name of the interface of the test double.
Prefix to use for the generated files.
Prefix used for test artifacts.
Dextool Tool version.
Custom header to prepend generated files with.
If an implementation of the interface for globals that zeroes them shall be generated.
Data pushed from the test double generator to be written to files.
During the translation phase the location of symbols that aren't filtered out are pushed to the variant.
Test double generation of C code.
TODO Describe the options.