Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #501, add PIC library for ut assert #504

Merged
merged 1 commit into from
Jun 23, 2020

Conversation

jphickey
Copy link
Contributor

Describe the contribution
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.

Fixes #501

Testing performed
Build and execute all unit tests.
Also test linking new PIC library into a CFE loadable app and running tests.

Expected behavior changes
No impact to current unit testing which runs UT assert as a standalone app.

System(s) tested on
Ubuntu 20.04

Additional context
Some functions were moved to support the alternative linking structure but no API/functionality changes. The moved functions include the buffer length extension that were originally part of PR #492.

Third party code
If included, identify any third party code and provide text file of license

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

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.
@jphickey jphickey added the CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) label Jun 16, 2020
@astrogeco
Copy link
Contributor

CCB 2020-06-17: APPROVED

@astrogeco astrogeco removed the CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) label Jun 18, 2020
@astrogeco astrogeco changed the base branch from master to integration-candidate June 22, 2020 19:42
@astrogeco astrogeco added IC-20200617 CCB:Approved Indicates code review and approval by community CCB labels Jun 22, 2020
@astrogeco astrogeco merged commit 2c35997 into nasa:integration-candidate Jun 23, 2020
@skliper skliper added this to the 5.1.0 milestone Aug 21, 2020
@jphickey jphickey deleted the fix-501-utassert-pic branch December 3, 2020 17:26
jphickey pushed a commit to jphickey/osal that referenced this pull request Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCB:Approved Indicates code review and approval by community CCB
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Offer secondary target for UT assert library that can be dynamically loaded
3 participants