Alter the sample app compiler flag to satisfy the cFS-GroundSystem

[BaldBeacon]

The latest commit of the cFS-Groundsystem includes glibc specific features specifically the inclusion of the struct addrinfo. The addrinfo struct definition is only exposed in gcc when passed a gnu compliant standard (the current test cmake definition uses -std=c99).

More information on the topic of C standard compliance vs the GNU libraries can be found on this stack overflow post: https://stackoverflow.com/questions/33076175/why-is-struct-addrinfo-defined-only-if-use-xopen2k-is-defined

[SpaceSteve121]

@BaldBeacon If this was added to a CFS dependency, shouldn't the build configuration of the relevant CFS repo have been updated to add that compiler flag in? Do we know why its up to the user to set a flag for a dependency of the CFS repo?

[BaldBeacon]

Since it's in the tools directory, from my knowledge the compilation options are sent by the user. If there was a means to say "only compile X tool with Y options" that would be the best case.

[BaldBeacon]

Due to some other problems with the current master of cFS (defined #38) this is on hold.