-
Notifications
You must be signed in to change notification settings - Fork 212
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
Minor fixes for cmake unit test build #97
Comments
Imported from trac issue 66. Created by jphickey on 2015-06-08T23:28:30, last modified: 2019-03-05T14:57:55 |
Trac comment by jphickey on 2015-06-08 23:36:03: Pushed commit [changeset:e99459e] for review |
Trac comment by jphickey on 2015-06-23 13:47:45: NOTE - this changeset will also be rolled into #103 as a prerequisite for those changes. |
Trac comment by jphickey on 2015-07-09 16:47:14: This is included in the {{{ic-2015-07-14}}} integration candidate for testing |
Trac comment by glimes on 2015-07-13 14:32:40: Accept. |
Trac comment by glimes on 2015-07-16 12:41:50: Included in [changeset:fe8f06c 2015-07-14 development merge], |
Trac comment by glimes on 2016-02-25 10:17:32: these will be fixed in CFE 6.5 |
Trac comment by jhageman on 2019-03-05 14:57:55: Milestone renamed |
The CFE unit test build was assuming the use of "-pg --coverage" options for gcc. Most targets do support this for coverage analysis however some do not (RTEMS, for example) as the runtime component of this feature may not be present in the target's c library. Therefore the UT build currently fails for these targets.
Also, the OSAL build scripts have a feature to allow installation of the unit test executables to the target binary directory. This is based on the value of a cmake variable called "INSTALL_TARGET_LIST", but the current build scripts are not setting this variable.
This ticket will
These are all fairly minor changes and only affect unit test.
The text was updated successfully, but these errors were encountered: