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

Integration Candidate 20200121 #490

Merged
merged 14 commits into from
Jan 27, 2020
Merged

Integration Candidate 20200121 #490

merged 14 commits into from
Jan 27, 2020

Conversation

skliper
Copy link
Contributor

@skliper skliper commented Jan 23, 2020

Describe the contribution
Fix #459, fix #355, fix, #24, fix #101, fix #412, fix #189

Testing performed
Steps taken to test the contribution:

  1. Current CI passes
  2. Enhanced CI in Add "const" to function prototypes where appropriate #40 passes debug/with deprecated elements testing

Expected behavior changes

  • Resolve doxygen warnings
  • add OMIT_DEPRECATED flag
  • Add strict warnings and enforce
  • Always increment sequence counter
  • Fix comments
  • Add code coverage test to evs

System(s) tested on

  • CI: Ubuntu 18.04

Additional context
N/A

Third party code
N/A

Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

anh and others added 14 commits January 8, 2020 11:19
Adds a "global_build_options.cmake" file akin to the existing
arch_build/mission_build option files.  Include an example of
this file that optionally does add_definitions() to omit the
deprected elements for build testing.
Add extra compile options for mission scope and arch scope.

These are separated to support cross compile environments that
do not/cannot use the same flags on both builds.

For "mission" build the targets are never cross compiled, only
built for the native host machine.  It should be safe to assume
a compiler in the GCC family and the strict warnings should
_always_ be applicable here.

For "arch" build the options are compiler vendor dependent.  The
file as-supplied can only be used if all the target cross compilers
are in the same family and support the same warning options.
However, this file can be modified without affecting the options
used for the host side tools.
Add a _custom suffix to differentiate the customization
file from the base file in the cmake directory.
Include in the basic warning set.  Note that at this time the CFE
does not build cleanly on all architectures with this warning enabled,
pending resolution of issue #313.
Adds logic and associated unit tests
Removes no-longer-used EID
Fix #101, Always increment sequence counter
Fix #412, Clean up table services comments/references
Fix #459, resolve doxygen obsolete warning
Fix #355, Add global scope option to omit deprecated items
Fix #189, Unit test for cfe_evs_task.c
@skliper skliper added this to the 6.8.0 milestone Jan 23, 2020
@skliper
Copy link
Contributor Author

skliper commented Jan 27, 2020

CCB 20200122 - Reviewed and approved for merge to master

@skliper skliper added the CCB:Approved Indicates code review and approval by community CCB label Jan 27, 2020
@skliper skliper merged commit 974cd68 into master Jan 27, 2020
@skliper skliper deleted the ic-20200121 branch January 27, 2020 15:24
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
4 participants