gaqku.blogg.se - How to install mingw-w64

If you're looking for Windows binaries then you need to download them from a third party who builds the source. consider removing unneeded documentation ( rm -r $pkgdir/usr/i686-w64-mingw32/share//lib/*.Mingw-w64 is an open source project and the developers provide source code only.for bigger projects, consider creating a separate -static package.because headers or CMake configuration files differ) consider installing static libraries into /usr/i686-w64-mingw32/static and /usr/x86_64-w64-mingw32/static if the shared and static build conflict (e.g.if the build system or project does not support this, build both separately.autotools-based projects often support building both in one go, when using mingw-w64-configure AUR shared and static libraries are both enabled.always build both shared and static libraries.

always use any as the architecture (except the package contains executables which must run on the build system).always put all stuff under the /usr/i686-w64-mingw32 and /usr/x86_64-w64-mingw32 prefix.always build both 32-bit and 64-bit versions of libraries.

always use and follow the original pkgver of the official package.always use the original pkgdesc and append (mingw-w64) to the end of pkgdesc.

always add !strip, staticlibs and !buildflags to options.

always add mingw-w64-gcc to makedepends, unless using mingw-w64-configure AUR or mingw-w64-cmake AUR.

always add mingw-w64-crt to depends, unless it depends on another package which implicitly depends on it.

Take a note of the following things though: Packaging for cross platform packages can be fairly tricky as there are many different build systems and low-level quirks. If a static variant of the package is being built, suffix the package name with -static (see below for the cases where this is necessary). A package for mingw-w64 should be named mingw-w64- pkgname.