[#104004] [Ruby master Feature#17883] Load bundler/setup earlier to make `bundle exec ruby -r` respect Gemfile — mame@...
Issue #17883 has been reported by mame (Yusuke Endoh).
21 messages
2021/05/24
[ruby-core:103687] [Ruby master Misc#17845] Windows Ruby - ucrt build?
From:
xtkoba+ruby@...
Date:
2021-05-01 19:33:31 UTC
List:
ruby-core #103687
Issue #17845 has been updated by xtkoba (Tee KOBAYASHI). I wonder if there is a standard target triplet for MinGW + UCRT. I came up with `x86_64-w64-mingw32-ucrt`, but when googled it hits only one page. I suppose something like `x64-mingw32-ucrt` is acceptable for `target_os` in `configure`, as there is a preceding example for Android: `aarch64-linux-android` vs `aarch64-linux` (GNU/Linux), although I have no idea whether it is sufficient to just suffix `target_os`. ---------------------------------------- Misc #17845: Windows Ruby - ucrt build? https://bugs.ruby-lang.org/issues/17845#change-91780 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal ---------------------------------------- Currently, Windows Ruby is normally compiled two ways. The first, mswin, is compiled using Microsoft's current Visual C compiler, and links to the universal runtime (ucrt). The second, mingw, is compiled using MinGW gcc. This links to msvcrt, an older version of Microsoft's Visual C runtime. Previously, all the MSYS2 MinGW packages linked to msvcrt. The MSYS2 project is now releasing build tools and packages linking to ucrt. MSYS2 has provided ruby packages, and GitHub user @Biswa96 contributed https://github.com/msys2/MINGW-packages/pull/8518, allowing Ruby to compile with ucrt. I tried the patch with ruby-loco, and it builds. There are some test issues, haven't had a chance to look at them yet. Normally, using exe/dll/so files together that use different versions of the runtime is not a good idea. Building extension gems with ucrt may provide gems that can be used with mswin, but can't be compiled due to issues with Visual C (vs gcc). Also, packages from the vcpkg project may be compatible with Ruby ucrt. The reason for this post is that Windows Ruby built with ucrt is essentially another platform, but the build 'looks like' a mingw build. This is really a third platform choice. What should it be called? Things like `CONFIG['RUBY_SO_NAME']`, `RUBY_PLATFORM`, etc? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>