Supported compilers, architectures, language versions

[rettichschnidi]

I could not find any documentation regarding targeted (supported) compilers/architectures/languages/etc. Did I miss something?

If not, my needs/proposal would be:

• Compilers:
  • Latest version of GCC
  • Latest version of Clang
• Architectures:
  • x86_64 on Linux
  • MIPSel 32 bit on Linux
  • ARMv5/armel 32 bit on Linux
• Language versions:
  • C99/C11: Fully supported
  • C90: Only for what might become a 1.x maintenance branch (❓ Future of 1.0 version ❓ #487). No longer supported in master, relieving the project from its restrictions.
  • C++: While Wakaama contains no C++ code, it must be usable from a C++ project.

[sbertin-telular]

My primary use is on a non-Linux system using the IAR compiler. It isn't practical to add my environment as supported, but I would not like to see any gcc/clang extensions used or Linux assumed outside of the examples. I would like for this to continue to be usable on constrained devices where running Linux isn't possible or practical.

[tuve]

My primary use is also on a non Linux system. On the embedded devices i think we run it with free rtos or bara bone on the mcu and then we also run it as a server as a library on iOS. I think there is also some (non linux) desktop use for testing as well.

[rettichschnidi]

My primary use is on a non-Linux system using the IAR compiler.

Which architecture? ARM? Something with less than 32 bits?

It isn't practical to add my environment as supported, but I would not like to see any gcc/clang extensions used or Linux assumed outside of the examples.

Regarding the extensions: How about adding a build configuration to CI which builds the "library" parts using -Wpedantic and "-Werror"?
Regarding non-Linux targets: Do you need Wakaama, client and/or server, to work with freestanding C implementations? Or is there some kind of OS?

[sbertin-telular]

I'm currently using an Arm Cortex-M3 based system, so 32-bit.

A CI build of the library parts with -Wpedantic and -Werror would probably be helpful.

I'm currently using an RTOS, but would like to see it continue to be possible to use it without an OS. As an example, adding mutexes (provided by the implementer) for thread safety would be OK, but requiring multiple threads would not. The mutex functions could then do nothing in a no-OS environment.

[rettichschnidi]

PR #575 will ensure Wakaama can be built with C99 (and C11) as well as keeping GNU specific compiler extensions out of the code base.

[tuve]

@rettichschnidi @sbernard31 can we close this?

[rettichschnidi]

From the points I wanted to address, just "C99/C11: Fully supported" and "x86_64 on Linux" have been fully implemented. Everything else is still open and/or implemented partially. Also, I'd like to have some kind of documentation about the decisions taken - having #586 would help with this.

[mlasch]

What should be the baseline platform we can safely rely on in Wakaama? I would assume we can use standard C functions (C99), but malloc and free are already wrapped in platform.c. memcpy in contrast is not wrapped.

I understand that we don't want to rely on Unix-like operating systems, but what about POSIX?

In #709 I want to use functions from benntoh and htobenn which clearly fall into the Unix-like category. I agree it might make sense here to have a more portable solution.

Finally, if we want to support RTOS/freestanding C implementations we should include a representative example in the build pipeline to guarantee support.