Support Ruby 3.1 UCRT binary

[ashie]

RubyInstaller has migrate from msvcrt.dll to ucrt.dll:
https://rubyinstaller.org/2021/12/31/rubyinstaller-3.1.0-1-released.html

So that symbols should be loaded from later one.
Althouth I considered introducing a new constant like UCRT_DLL, this
commit still using MSVCRT_DLL even if Ruby is run on ucrt.dll to keep
backward compatibility. I think replacing MSVCRT_DLL with UCRT_DLL
is almost meaningless, they won't used at same time.

Signed-off-by: Takuro Ashie [email protected]

[ashie]

See also:

• Simplify WindowsFile fluent/fluentd#3774 (comment)
• Tail plugin does not parse the path if path contains folder with multibyte characters (e.g. Chinese) on windows while it works on fluentd image in linux docker. fluent/fluentd#3769 (comment)

[ashie]

Oops, CI (AppVeyor) failed on Ruby 3.1...

[ashie]

Succeeded on GitHub Actions:
ashie#2

What's wrong?

[ashie]

Oops, CI (AppVeyor) failed on Ruby 3.1...

Hmm, it tried to build win32-api and failed on Ruby-3.1.
On other Ruby versions, win32-api universal-mingw32 is used.
Probably we need to run with ridk exec on Ruby 3.1.

[cosmo0920]

Oops, CI (AppVeyor) failed on Ruby 3.1...

Hmm, it's tried to build win32-api and failed on Ruby-3.1. On other Ruby versions, win32-api universal-mingw32 is used. Probably we need to run with ridk exec on Ruby 3.1.

I tried to use ridk exec for Ruby 3.1 and other ridk available Rubies. But, it didn't succeeded to build win32-api extension gem.

• https://ci.appveyor.com/project/cosmo0920/windows-api/builds/43794625
• 43cc42c

So, we might have to keep AppVeyor's CI task entries from Ruby 2.0 to Ruby 3.0.
For Ruby 3.1 or later, we have to use GitHub Actions for CI.

[ashie]

I tried to use ridk exec for Ruby 3.1 and other ridk available Rubies. But, it didn't succeeded to build win32-api extension gem.

I succeeded to build it on x86_64 but not yet on x86:
https://ci.appveyor.com/project/ashie/windows-api/builds/43793998

[cosmo0920]

In my thoughts, we can drop Ruby 3.1 x86 from CI target.
This is because we don't have actual use case for 32bit version of td-agent packaging requirements on Windows.

[cosmo0920]

Looks attractive for me.

[ashie]

Thanks!