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
Is your feature request related to a problem? Please describe.
The current UT assert is designed to be statically linked as an OSAL application.
To support a CFE functional test environment that uses the same UT assert reporting methods, the library should offer a target that can be linked as loadable module.
Describe the solution you'd like
The differences are:
Compile as position independent code (PIC) so it can be linked into a dynamic module.
Separate out the OS_Application_Startup and OS_Application_Run - as this will be loaded into a larger app, not a standalone app, and these symbols are already defined.
Consolidate global variables into a common structure and make early init/reset of these variables into a separate routine from OS_Application_Startup.
Additional context
This dynamically-loadable variant can be a separate target, so it shouldn't change anything about the existing apps/tests that link with the existing static "ut_assert" library.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Add a position independent code (PIC) variant of the ut_assert library,
which can be dynamically loaded into other applications rather than running
as a standalone OSAL application. This enables loading UT assert as a
CFE library.
This required moving some symbols/functions around. Mainly, the PIC
library does _not_ contain the "utbsp.c" file which has the bindings
to the OSAL BSP when running as a standalone app, but everything else
should be the same.
Is your feature request related to a problem? Please describe.
The current UT assert is designed to be statically linked as an OSAL application.
To support a CFE functional test environment that uses the same UT assert reporting methods, the library should offer a target that can be linked as loadable module.
Describe the solution you'd like
The differences are:
Additional context
This dynamically-loadable variant can be a separate target, so it shouldn't change anything about the existing apps/tests that link with the existing static "ut_assert" library.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: