* Refactored type organization
* Creating better configuration/types header hierarchy
* Replace FpConfig type aliases with FPP generated aliases
* Add the aliases to the FPP model
* Config + Type Aliases builds
* Renamed Fw/Types.h,hpp to Fw/FPrimeBasicTypes.h,hpp
* Updating to FPP-a7
* Adding newline
* sp
* Fixing minor nit from review
* Spurious ;
---------
Co-authored-by: Andrei Tumbar <andrei.tumbar@jpl.nasa.gov>
* Pull in framework changes from data-products branch
* Pull in changes to DpManager from data-products branch
* Pull in DpWriter from data-products branch
* Fix spelling
* Revise FileNameString
* Fix warnings in CI
* Fix static analysis warnings
* Fix static analysis warnings
* Revise formatting and comments
* Revise banner comments
* Revise FileNameString per PR comment
* Revise path names in config headers
If a header H.hpp exists in the F Prime source base, then
is dangerous. Because [project root] and [fprime root] are both
in the list of include paths, it's not clear whether this means "include
[project root]/config/H.hpp" or "include [fprime root]/config/H.hpp."
On the other hand,
or
has no such ambiguity, because only one of [project root]/config
and [fprime root]/config is in the list of include paths.
* Revise path names in config headers
If a header H.hpp exists in the F Prime source base, then
`#include "config/H.hpp"`
is dangerous. Because [project root] and [fprime root] are both
in the list of include paths, it's not clear whether this means "include
[project root]/config/H.hpp" or "include [fprime root]/config/H.hpp."
On the other hand,
include <config/H.hpp>
or
`#include "config/H.hpp"`
has no such ambiguity, because only one of [project root]/config
and [fprime root]/config is in the list of include paths.
