When -u is enabled, only unit test base class code should be generated, not component autocode.
Add a flag -a (automatic test setup) to govern the generation of TesterHelpers.cpp. When -a is present, TesterHelpers.cpp is generated when -u is present and -t is not present. Otherwise TesterHelpers.cpp is generated when -u and -t are both present.
fpp-filenames
Add an -a flag and make the behavior match that of fpp-to-cpp.
fpp-depend
Eliminate the -t option. If necessary in the next round of integration, we can write generated template files to separate files with the suffix .template. This may not be necessary, depending on how the integration is done.
Have the -u flag write the unit test base class files (and only those files) to a separate file, instead of adding the unit test files to the autocoded files reported by -g.
Add an -a flag. When -a is present,TesterHelpers.cpp is included with the autocode files reported by -u. Otherwise it is not so included.
Changes requested during the F Prime integration:
fpp-to-cpp
-u
is enabled, only unit test base class code should be generated, not component autocode.-a
(automatic test setup) to govern the generation ofTesterHelpers.cpp
. When-a
is present,TesterHelpers.cpp
is generated when-u
is present and-t
is not present. OtherwiseTesterHelpers.cpp
is generated when-u
and-t
are both present.fpp-filenames
-a
flag and make the behavior match that offpp-to-cpp
.fpp-depend
-t
option. If necessary in the next round of integration, we can write generated template files to separate files with the suffix.template
. This may not be necessary, depending on how the integration is done.-u
flag write the unit test base class files (and only those files) to a separate file, instead of adding the unit test files to the autocoded files reported by-g
.-a
flag. When-a
is present,TesterHelpers.cpp
is included with the autocode files reported by-u
. Otherwise it is not so included.Tasks