Builds on mac.
Describe the contribution A clear and concise description of what the contribution is.
- Include explicitly what issue it addresses [e.g. Fixes #X]
Testing performed Steps taken to test the contribution:
- Build steps '...'
- Execution steps '...'
Expected behavior changes A clear and concise description of how this contribution will change behavior and level of impact.
- API Change: xxx (if applicable)
- Behavior Change: xxx (if applicable)
- Or no impact to behavior
System(s) tested on
- Hardware: [e.g. PC, SP0, MCP750]
- OS: [Mac OSX]
- Versions: [e.g. cFE 6.6, OSAL 4.2, PSP 1.3 for mcp750, any related apps or tools]
Additional context Add any other context about the contribution here.
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 Full name and company/organization/center of all contributors ("Personal" if individual work)
- If NASA Civil Servant Employee or GSFC Contractor on SES II
- Address/email/phone and contract/task information (if applicable) must be on file
Not sure if this is wanted or not.
This was pulled from https://gist.github.com/yinyin/2027912
im trying to port cfs to mac via a qt osal layer.
Related to #95. Suggestion is to remove endian.h dependency all together in favor of a custom/portable set of conversion functions.