WSL VS setup-msys2

👉 Baixar WSL 2.3.24 (MSI)

Microsoft's DirectX C++ example code needs to interact with DirectX' C APIs. That will easily lead to "C with classes" C++ when most of the code is interacting with foreign APIs, like these API demos do.

I think open-source software like https://github.com/microsoft/WSL is probably more representative of what modern C++ companies look like. Plenty of files that just interact with OS C APIs, but no shortage of modern C++ features in use.

Microsoft continues to be a major contributor to open source and announced a couple major projects moving from closed-source to the open on GitHub. The first is a long-time coming project, the Windows Subsystem for Linux (WSL). I first used WSL to port a Java stack to Windows. That stack was a nightmare to run on Windows due to a team optimizing for macOS workflows but we wanted to enable new developers to use standard Windows dev machines and stop requiring expensive macOS hardware for a cross-platform native toolchain like Java. Today, WSL is a major part of the Windows developer experience. And now, Microsoft is open-sourcing WSL to allow the community to contribute and innovate on the project on GitHub.

https://github.com/microsoft/WSL/issues/9049#issuecomment-26...

WSL GitHub Repository

https://github.com/microsoft/WSL/issues/7973#issuecomment-27...

Is there a way to push this without tripping the corporate auto-close bot?

If you are running Microsoft Windows, I want to advise one more prerequisite step that you need to take before getting started with Python or uv: install the Windows Subsystem for Linux, also known as WSL2. Do not, for the love of all that is good and holy, try and install Python tooling directly in Windows; install WSL first. This guide outlines all the steps you need to take to get started, though I recommend downloading WSL from the Releases page on Github instead of from the Microsoft Store as advised in Step 3.

/? mingw: https://github.com/search?q=mingw&type=repositories

msys2/MINGW-packages: https://github.com/msys2/MINGW-packages ; [..., SDL, gles, glfw, egl, glbinding, cargo-c, gstreamer, gtest, cppunit, gtk4, icu, jack2, gnome-text-editor, gtksourceview, kdiff3, libgit2, libusb, libressl, libsodium, libserialport, libslirp, hugo]

msys2/setup-msys2: https://github.com/msys2/setup-msys2:

> setup-msys2 is a GitHub Action (GHA) to setup an MSYS2 environment (i.e. MSYS, MINGW32, MINGW64, UCRT64, CLANG32, CLANG64 and/or CLANGARM64 shells)

Though, if you're writing a 3d app/game, e.g. panda3d already builds for Windows, Mac, and Linux.

panda3d > Building applications: https://docs.panda3d.org/1.11/python/distribution/building-b... :

mstorsjo/llvm-mingw:

Other pages provide complementary information on that same topic.

Another thing I appreciated was the explanation of MSYS2's environments:

https://www.msys2.org/docs/environments/

Being able to painlessly switch away from MSVCRT to UCRT was helpful in solving some UTF-8 difficulties I was experiencing at the time.

Package management with pacman is rather pleasant, and the setup-msys2 GitHub Action makes it simple to provide your GHA workflow with the tools and libs you want:

https://www.msys2.org/docs/package-management/

https://packages.msys2.org/queue

https://github.com/msys2/setup-msys2

> Actions reduce workflow steps by providing reusabe[sic] “code” for common tasks. To run an action, you include the uses keyword pointing to a GitHub repo with the pattern {owner}/{repo}@{ref} or {owner}/{repo}/{path}@{ref} if it’s in a subdirectory. A ref can be a branch, tag, or SHA.

Aside from the typo, I wonder how many packages could be backdoored at once, if an action maintainer went rogue, seeing as there's no pinning for actions by default, and (according to https://github.com/msys2/setup-msys2/blob/main/HACKING.md) moving a tag is the default way to push updates to an action. (Interestingly get-cmake/run-cmake/run-vcpkg are all operated by the same person.)