I recently updated to version 14.0.0+. Also, unlike the previous version, you can now use the latest version without the maintainer creating a bump commit. If you encounter any issues, please let me know in the comments. Enjoy!
Search Criteria
Package Details: mingw-w64-headers-git 14.0.0.r65.gb536c4fdb-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mingw-w64-headers-git.git (read-only, click to copy) |
|---|---|
| Package Base: | mingw-w64-headers-git |
| Description: | MinGW-w64 headers for Windows (git version) |
| Upstream URL: | https://www.mingw-w64.org/ |
| Licenses: | LicenseRef-custom |
| Groups: | mingw-w64, mingw-w64-toolchain |
| Conflicts: | mingw-w64-headers |
| Provides: | mingw-w64-headers |
| Submitter: | ant32 |
| Maintainer: | hwangsihu |
| Last Packager: | hwangsihu |
| Votes: | 11 |
| Popularity: | 0.000000 |
| First Submitted: | 2015-01-28 04:39 (UTC) |
| Last Updated: | 2026-06-03 04:31 (UTC) |
Required by (4)
- bakkesmod-steam-git (requires mingw-w64-headers) (make)
- wine-osu-spectator (requires mingw-w64-headers) (make)
- wine-osu-spectator-wow64 (requires mingw-w64-headers) (make)
- winfile (requires mingw-w64-headers) (make)
Sources (1)
hwangsihu commented on 2026-06-08 11:48 (UTC) (edited on 2026-06-08 11:51 (UTC) by hwangsihu)
telgar commented on 2020-02-26 08:43 (UTC) (edited on 2020-02-26 08:43 (UTC) by telgar)
The direct-x headers were removed in Jan 2020, so these lines now cause an error:
install -Dm644 "${srcdir}/mingw-w64/mingw-w64-headers/direct-x/COPYING.LIB" "${pkgdir}/usr/share/licenses/${pkgname}/direct-x-COPYING.LIB"
install -Dm644 "${srcdir}/mingw-w64/mingw-w64-headers/direct-x/readme.txt" "${pkgdir}/usr/share/licenses/${pkgname}/direct-x-readme.txt"
pingplug commented on 2018-02-14 13:26 (UTC)
bootstrap:
mingw-w64-binutils-->mingw-w64-headers-bootstrap-->mingw-w64-headers-git-->mingw-w64-gcc-base-->mingw-w64-crt-git-->mingw-w64-winpthreads-git-->mingw-w64-gcc
update form non-git version:
mingw-w64-headers-git-->mingw-w64-crt-git-->mingw-w64-gcc-->mingw-w64-winpthreads-git-->all other mingw-w64-* packages must be rebuild
rubenvb commented on 2013-09-19 07:22 (UTC)
Sorry for not replying to all the pleas for help :s I was on holiday and have been quite busy lately.
MinGW-w64 is nearing v3 release, which will hopefully stop everyone trying to work around svn version breakage. The release is tested by the Fedora MinGW-w64 cross-compiler maintainer on a lot of packages (including qt5), so it should be nearly flawless when it's out, and keep continued usability regardless of the current MinGW-w64 development in SVN. I have informed the MinGW-w64 team it was a bad idea to require trunk for a stable GCC, and they will try their best to not have this happen again. I'm in the process of testing new PKGBUILDs (for SVN currently). I will switch all these back to MinGW-w64 v3.0 stable once it's out.
Thank you for your patience :-)
ant32 commented on 2013-09-18 22:39 (UTC)
I wrote rubenvb an email 2 weeks ago and he hasn't replied. If mingw-w64-gcc also had gcc-make-xmmintrin-header-cplusplus-compatible.patch we'd also not need mingw-w64-gcc-qt5. I'm not sure if he is still fully maintaining this http://sourceforge.net/mailarchive/message.php?msg_id=31087007.
Auguste commented on 2013-09-18 04:19 (UTC)
is it possible to configure with --enable-secure-api?
it is required by some source, like mingw-w64-angleproject, which is in turn required by mingw-w64-qt5-base.
the final outcome with secure api enabled has 0.00MB difference to the current one, according to pacman.
usch commented on 2013-08-21 14:53 (UTC)
@ant32 thanks for the link to your repo.
svn checkout of the latest version would be enough to compile,
but how to change this behaviour of makepkg?
usch commented on 2013-08-21 13:36 (UTC)
@ant32 thanks for the link to your repo.
svn checkout of the latest version would be enough to compile,
but how to change this behaviour of makepkg?
Pinned Comments
hwangsihu commented on 2026-06-08 11:48 (UTC) (edited on 2026-06-08 11:51 (UTC) by hwangsihu)
I recently updated to version 14.0.0+. Also, unlike the previous version, you can now use the latest version without the maintainer creating a bump commit. If you encounter any issues, please let me know in the comments. Enjoy!