Questions about openOSC and __STRICT_ANSI__ #17
Description
There is a lot of source in a project I work in, most of it historic and from a variety of different developers. We are implementing OpenOSC into this platform, but top-level build system supplies a suggested C standard. In the case of C++, C++17. And, it does this with -std=c++17.
Unfortunately, gcc supplies STRICT_ANSI when any of the c++ std's are used. While it's possible to change the build process to suggest "gcc+17", or not specify a standard at all, the original point of specifying a standard was to help the developers all stay in a similar frame, and to update/change any code when that is needed. Shifting away from a proper standard to a GNU variant of a standard just feels opposed to the point in a way.
I assume this is a problem many have faced. Are there any ideas beyond changing the standard requested of the compiler? Is there a way to tell OpenOSC "No, enable yourself anyway," and/or does STRICT_ANSI really prohibit it's use completely?