MSYS2-packages
win32metadata
MSYS2-packages | win32metadata | |
---|---|---|
10 | 27 | |
1,250 | 1,281 | |
0.7% | 0.5% | |
9.8 | 0.0 | |
5 days ago | about 19 hours ago | |
Shell | C++ | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MSYS2-packages
- How to start msys2-shell with fish-shell
-
MSYS2 Installation
Google says (1, 2, 3) that this issue is caused by Avast/AVG antivirus moving some executable files (bash.exe in your case, seemingly) into its quarantine folder.
-
Colorscheme problems when using MinTTY as the terminal for nvim.
It's a known issue: https://github.com/msys2/MSYS2-packages/issues/3150
-
Erdtree v1.4.1 - the love child of `tree` and `du`, now with support for a configuration file to override defaults and more
Could you let me know of this is perhaps relevant to you? I will investigate sometime this week! Thanks for bringing this to my attention.
-
Windows Subsystem For Linux a.k.a. WSL 1.0.0 released
I am still on WSL1 due to the filesystem performance with WSL2. I recently tried to move more of my workflow towards MSYS2 but various things keep breaking for me without obvious reasons.
Latest issue I encountered was that GNU parallel simple does not work. [1]
[1]: https://github.com/msys2/MSYS2-packages/issues/3289
-
Getting GTK3 in WINE?
I've already tested the rest of the tools needed for the build process (just Python 3.10 and PyInstaller) and they seem to work fine. My issue is that both MSYS2 and Cygwin do not work in WINE (this is pretty well documented: MSYS2, Cygwin), so I don't know of any other means of getting the Windows versions of GTK3 libraries in my WINE prefix so that PyInstaller can pack it all up for me.
- Bug on fresh installation · Issue #2295 · msys2/MSYS2-packages
- zsh completion issue · Issue #38 · msys2/MSYS2-packages
-
copy_file with overwirte_existing throws exception when the file exists
It's old bug with gcc standard library implementation which has not been fixed, I guess most likely nobody made a bug report. I tested it myself and indeed it doesn't work properly and we are not alone: https://github.com/msys2/MSYS2-packages/issues/1937.
-
The Atrocities of COM win32 headers
My last experience with MinGW-w64 was when I was trying to compile my C++ simulation code in Windows and finding out that AVX instructions were not working because the compiler had misalignment-related bugs. (The issue is still open in https://github.com/msys2/MSYS2-packages/issues/1209)
MinGW/MSYS certainly had appeal to former Linux devs who didn't want to touch the horrors of MSVC, but Zig (with its included Clang compiler/runtime) might end up being a better solution for people trying to compile C/C++ code on Windows in a stable manner.
win32metadata
-
Hey Rustaceans! Got a question? Ask here (18/2023)!
As /u/huellenoperator notes, that this needs a pointer to a mutable string comes straight from microsoft through win32metadata. Maybe it's a mistake on Microsoft's side, but if it's not you're taking big risks.
-
Kernel Headers for Windows could soon make it into windows-rs
Microsoft offers official "bindings" to Win32 APIs through win32metadata. However, until recently, it did not include metadata for kernel-level functions or WDK. In early 2021, an issue was raised through windows-rs regarding this limitation, but progress was slow until now. Microsoft has finally released official metadata for WDK, which can be found on the wdkmetadata repository. The latest comment on the issue thread can be found here:
-
winreader: read memory from other programs
for win32metadata's kernel api tracking issue, https://github.com/microsoft/win32metadata/issues/401
-
Best windows stubs
Any examples? Since the API bindings in windows-sys are generated from the metadata generated from official Windows SDK headers I'd not expect to see this kind of difference.
-
can we be free of c?
You might also look at this project: https://github.com/microsoft/win32metadata
-
Is it time to retire C and C++ for Rust in new programs?
There is still the occasional incredibly subtle link time fuckery in Rust.
https://github.com/microsoft/win32metadata/issues/1274
"Minor" semver updates to crates breaking things via e.g. unexpected MSRV bumps is pretty common too, with some resulting bitrot. That said, I agree with you that things in Rust are at least better. Imperfect, but better.
-
Are there any Windows-centric perks of using C# that other non-Microsoft languages simply can't offer (or at least don't out of the box)?
Win32 is available as metadata to enable adoption in as many languages as possible. Are there some things missing? Yes. The Microsoft team acknowledges that and encourages asking for the things you need so they can add them to the metadata.
-
Using Windows API in Julia?
It might be interesting to have bindings generated for the entirety of Win32 API through https://github.com/microsoft/win32metadata
- Would std code for Windows ever use the windows crate by Microsoft?
-
The Atrocities of COM win32 headers
Hi JB! Funny to cross paths with you in this context. I don't know if you remember me but I was a rookie programmer who got the pleasure of joining the VideoLan Conference in Dublin back in 2014, and then Paris the next year, and you were very kind to me.
The GitHub issue title here is unfortunately misleading. I have renamed it to "ideas to improve windows header files and libc". Also, I hope it is clear that I rebutted the points made by the OP, because I completely agree with your summary that the mingw-w64 people are skilled, nice and very clever and think about all use cases.
If any drive-by HN readers work at Microsoft, please help us with this issue: https://github.com/microsoft/win32metadata/issues/766
What are some alternatives?
mingw-w64 - (Unofficial) Mirror of mingw-w64-code
rust-bindgen - Automatically generates Rust FFI bindings to C (and some C++) libraries.
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
JNA - Java Native Access
glibc-abi-tool - A repository that collects glibc .abilist files for every version and a tool to combine them into one dataset.
go - The Go programming language
media-autobuild_suite - This Windows Batchscript helps setup a Mingw-w64 compiler environment for building ffmpeg and other media tools under Windows.
winapi - Windows API declarations without <windows.h>, for internal Boost use.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
qmk_distro_msys - A Windows one-click installer for the QMK CLI
panama-foreign - https://openjdk.org/projects/panama