You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason, many CFS apps instantiated their tables (in C structs) qualified as static. This serves no useful purpose but it breaks the edscfetbl tool which expects to be able to find the symbol by name.
While a workaround is simple (remove static) to get the table to build, this feature of supporting C struct table definitions was intended for backward compatibility, so it would be better if it worked without needing to modify the original table definitions. Having to modify the original table def somewhat defeats the purpose. It seems most, if not all CFS apps have defined the table using static.
Need There may be a way to work around this via the CFE_TBL_FILEDEF macro and possibly tweaking the build rule.
Filing this bug against eds2cfetbl for now, but the fix might involve CFS CMake table build rule changes as well. Need to investigate so this seems like the best place to start.
The text was updated successfully, but these errors were encountered:
For some reason, many CFS apps instantiated their tables (in C structs) qualified as
static
. This serves no useful purpose but it breaks theedscfetbl
tool which expects to be able to find the symbol by name.While a workaround is simple (remove
static
) to get the table to build, this feature of supporting C struct table definitions was intended for backward compatibility, so it would be better if it worked without needing to modify the original table definitions. Having to modify the original table def somewhat defeats the purpose. It seems most, if not all CFS apps have defined the table using static.Need There may be a way to work around this via the CFE_TBL_FILEDEF macro and possibly tweaking the build rule.
Filing this bug against eds2cfetbl for now, but the fix might involve CFS CMake table build rule changes as well. Need to investigate so this seems like the best place to start.
The text was updated successfully, but these errors were encountered: