FreeBSD CI

[bsdcode]

Added FreeBSD x64 to CI and updated COMPILING to be more consistent with the CI.

Arm64 throws the following errors:

In file included from /home/runner/work/Ymir/Ymir/apps/ymir-sdl3/src/app/stb_implementations.cpp:4:
/home/runner/work/Ymir/Ymir/vendor/stb/stb/stb_image_write.h:354:59: error: non-const lvalue reference to type '__builtin_va_list' cannot bind to a value of unrelated type 'va_list' (aka 'std::__va_list')
  354 |          case '1': { unsigned char x = STBIW_UCHAR(va_arg(v, int));
      |                                                           ^
/usr/local/llvm19/lib/clang/19/include/__stdarg_va_arg.h:20:43: note: expanded from macro 'va_arg'
   20 | #define va_arg(ap, type) __builtin_va_arg(ap, type)
      |                                           ^~
/home/runner/work/Ymir/Ymir/vendor/stb/stb/stb_image_write.h:248:42: note: expanded from macro 'STBIW_UCHAR'
  248 | #define STBIW_UCHAR(x) (unsigned char) ((x) & 0xff)
      |                                          ^

I currently don't know what's the cause for this error, seems something specific to FreeBSD arm64 and maybe even the compiler. Because I don't have a arm64 system to debug and test, I excluded this architecture from CI for now.

While there, fixed the (intended) Ymir_ENABLE_IPO usage in the CI.

[StrikerX3]

Arm64 throws the following errors:
[elided]
I currently don't know what's the cause for this error, seems something specific to FreeBSD arm64 and maybe even the compiler. Because I don't have a arm64 system to debug and test, I excluded this architecture from CI for now.

That's completely fine. Ymir technically builds on Windows ARM64 as well, but the build script doesn't include this target because the runner image lacks Ninja.

While there, fixed the (intended) Ymir_ENABLE_IPO usage in the CI.

Thanks for catching that! I was wondering why the option had no effect...