Inconsistent default CPU ID/Spacecraft ID between PC-Linux and other platforms

[johnphamngc]

Describe the bug
The CPU ID/Spacecraft ID on Linux differs from the VxWorks build due to the Linux build deriving the value from the targets.cmake and other platforms deriving it from the value of [target name]_platform_cfg.h and [mission name]_mission_cfg.h

To Reproduce
Set CFE_MISSION_SPACECRAFT_ID in [mission name]_mission_cfg.h different than SPACECRAFT_ID in targets.cmake. Do same for CFE_PLATFORM_CPU_ID and the value in TGT. Build for Linux and a VxWorks target. CPU IDs will be different when attempting to run SBN

Expected behavior
The same default CPU IDs should show up across both platforms.

Code snips
It appears this is due to the Linux PSP using GLOBAL_CONFIGDATA in CFE's target_config.c and the other platforms using CFE_MISSION_SPACECRAFT_ID and CFE_PLATFORM_CPU_ID directly.

System observed on:

• OS: [e.g. Linux 4.4]
• Versions cFE 6.7.12 , PSP 1.4 for mcp750, Linux, sp0

Additional context
Add any other context about the problem here.

Reporter Info
John Pham, Northrop Grumman

[jphickey]

FYI - as part of the exception handling changes in pull #160 this also updated the way these IDs are handled. The MCP750 implementation now matches the Linux and RTEMS in this regard.

[skliper]

@johnphamngc Feel free to reopen if the update referenced above (now in master) didn't resolve your issue.

[johnphamngc]

Should a bug/enhancement be filed against cFE to deprecate CFE_PLATFORM_CPU_ID, CFE_PLATFORM_CPU_NAME, CFE_MISSION_SPACECRAFT_ID as they're now configured by TGT_NAME, and SPACECRAFT_ID cmake variables?

[skliper]

Should a bug/enhancement be filed against cFE to deprecate CFE_PLATFORM_CPU_ID, CFE_PLATFORM_CPU_NAME, CFE_MISSION_SPACECRAFT_ID as they're now configured by TGT_NAME, and SPACECRAFT_ID cmake variables?

See nasa/cFE#710