| 1 |
On Thu, Jan 14, 2021, at 5:38 AM, Fabian Groffen wrote: |
| 2 |
> Please chime in if you have an opinion, info, interest, etc. |
| 3 |
> |
| 4 |
|
| 5 |
Chiming in to state the platforms are all subtly different. Cygwin |
| 6 |
is POSIX compliant (or tries to be) and allows access to the underlying |
| 7 |
Windows APIs while WSL does not generally allow access to the rest |
| 8 |
of the system. |
| 9 |
|
| 10 |
MSYS2 does not aim for full POSIX compliance but does |
| 11 |
try to offer a familiar build environment. It also supplies a package |
| 12 |
manager CLI. |
| 13 |
|
| 14 |
When I help someone support Windows as a target I typically suggest |
| 15 |
using MSYS2. Server or containerized workloads are easily relocated |
| 16 |
to WSL2 but many user facing programs can not be moved to WSL2. |
| 17 |
|
| 18 |
I am not exactly sure this helps. |
| 19 |
|
| 20 |
I was not aware of the winnt target. |
| 21 |
I will see if it is useful for my purposes, as (as usual) I get annoyed |
| 22 |
by package managers not having the latest packages and needing |
| 23 |
to build them myself in MSYS2. |
| 24 |
|
| 25 |
Is it possible to briefly describe the challenges of the targets? |
Archives